Dieter Maurer <dieter@handshake.de> writes:
Diego Rodrigo Neufert writes:
<dtml-in "_.range(1000)"> ....code... <dtml-if valueOk> STOP THE LOOP </dtml-if> </dtml-in> A long time ago, someone has implemented a "dtml-break" tag.
Wow. That's good to know. I just created some fairly ugly code to get around the lack of something like a dtml-break. I just tried searching for it on zope.org, on the mailing lists, and using google for good measure. Didn't find any mention of it anywhere. If anybody does come up with a link I'd love to see it. I wonder why there's nothing like that natively..? //glw
http://www.zope.org/Members/jfarr/Patches/dtml-break I requested that this page be cataloged but it never was. I also submitted it as a patch to the distribution but it was refused. Something about a new dtml-in implementation that I haven't seen materialize in the last 5 versions or so. I would use patch with the diff file rather than overwriting your existing files since these patches were made to 2.1.6. --jfarr ----- Original Message ----- From: "Geoffrey L. Wright" <geoff@northernwastes.org> To: <zope@zope.org> Sent: Wednesday, January 17, 2001 3:04 PM Subject: Re: [Zope] Stopping a <dtml-in>
Dieter Maurer <dieter@handshake.de> writes:
Diego Rodrigo Neufert writes:
<dtml-in "_.range(1000)"> ....code... <dtml-if valueOk> STOP THE LOOP </dtml-if> </dtml-in> A long time ago, someone has implemented a "dtml-break" tag.
Wow. That's good to know. I just created some fairly ugly code to get around the lack of something like a dtml-break.
I just tried searching for it on zope.org, on the mailing lists, and using google for good measure. Didn't find any mention of it anywhere. If anybody does come up with a link I'd love to see it.
I wonder why there's nothing like that natively..?
file://glw
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
Hi, I have a folder with a property. Different people visiting this folder will read/write this property. When there's many concurrent visitors, is Zope able to make sure the read/write request is in the first-in-first-serve order? Cheers Dirksen __________________________________________________ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/
On Thu, 14 Jun 2001, Dirksen wrote:
Hi,
I have a folder with a property. Different people visiting this folder will read/write this property. When there's many concurrent visitors, is Zope able to make sure the read/write request is in the first-in-first-serve order?
Zope will handle the concurrency with no problem. The only problem you may have is if lots of users write to the property at the same time. Then you might get a ConflictError. See: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/zope-devel/DevGuide/Persisten... for more information on conflicts. It won't be a problem as long as you don't hammer the property with writes. -Michel
The only problem you may have is if lots of users write to the property at the same time. Then you might get a ConflictError. See:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/zope-devel/DevGuide /Persistence.stx?rev=1.21&content-type=text/vnd.viewcvs-markup
for more information on conflicts. It won't be a problem as long as you don't hammer the property with writes.
-Michel
So, basicly it doesn't handle concurrency. Yes, multiple users can "view", but isn't that what a web server is supposed to do? The real issue of "concurrency" is whether it handles multiple users trying to write to a property at the same time. Obviously, the answer is no. It would be nice if I could find some way to "Lock" a transaction, similiar to ColdFusion's <CFLock> tag. Tommy
Tommy Johnson wrote:
The only problem you may have is if lots of users write to the property at the same time. Then you might get a ConflictError. See:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/zope-devel/DevGuide /Persistence.stx?rev=1.21&content-type=text/vnd.viewcvs-markup
for more information on conflicts. It won't be a problem as long as you don't hammer the property with writes.
-Michel
So, basicly it doesn't handle concurrency.
No, it does handle concurrency via an optimistic concurrency control strategy.
Yes, multiple users can "view", but isn't that what a web server is supposed to do? The real issue of
Multiple users can write too. The point is that performance begins to degrade when lots of writes are happening at the same time.
"concurrency" is whether it handles multiple users trying to write to a property at the same time. Obviously, the answer is no.
This is incorrect.
It would be nice if I could find some way to "Lock" a transaction, similiar to ColdFusion's <CFLock> tag.
There's no need. Just let the application server handle it.
participants (6)
-
Chris McDonough -
Dirksen -
Geoffrey L. Wright -
Jonothan Farr -
Michel Pelletier -
Tommy Johnson