>From multiple windows to double click, if you use Tapestry sooner or later you will run into problem like this: page recorder locked, synchronization issue on the engine... etc. Let's just say you are not alone and hoping that will fix in the up coming 3.1/4.0 release (and I am still interested to hear other people work around and how is it going to fix in 3.1/4.0)
And I agree with you, this is not nonsense. I cannot tell my boss that our customer is acting stupid (even often time they are) when the customer has problem on website, they will call support, and support will call developer and ask for a fix. I just can't say that we will not be able to do anything about the page recorder lock error because your client is double clicking/multi-windows... They want solution, so over time there are some work around and you can search the mailing list for some. But i just feel that this should address in the framework. I still love tapestry thou' -- Regards, Stephen Yau 引用 "T.Mikov" <[EMAIL PROTECTED]>: > Todd O'Bryan wrote: > > Remember that every session has its own copy of Visit, so the only > > problems you would have would be created by a _single user_ accessing > > Visit from more than one thread. That could happen, but it would involve > > either multiple pages being accessed concurrently or someone being > > click-happy. Either way, they should maybe expect to get nonsense. > > Hmm. I myself often open more than one window from the same session; > with Amazon for example. I never expect to get nonsense. > > I am not completely sure, but it seems that working with more than one > browser window and a very slow modem connection makes this more likely > to happen. If it takes 10-20 seconds to load a page, it is very > conceivable that the user might click more than once in different windows. > > Plus, getting nonsense is just one possibility. Who knows what else > could happen - data corruption, exceptions. Deliberate denial of service > attacks ?? > Once the possibility for a problem exists, even though it is under what > we think are very rare circumstances, nothing is certain anymore. > > Anyway, I think I got my answer. The application should provide > synchronization for the visit object, if this is considered a problem. > Whether it is a problem depends on perspective. > > Thanks a lot to everybody who responded. I am a Tapestry newbie so > perhaps I will be picking your brains more in the coming weeks ! :-) > > regards, > Tzvetan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
