Hi Francky, Thanks for the time you take to answer me.
> In this process, there are 2 approaches, quite different > . > What I think is very frustrating is to fill up a form (can be long), > and find out that your time is lost because someone was quicker than > you to post. > You're right and it's obvious. I practices other languages in the past and, 'cause I didn't use Internet, I didn't have this kind of problem (Oracle Forms handles this quite well, but, of course, it's not the same technology). In facts, as soon as a user modify a record on his screen, the record is locked. I wonder if it could be done this with Ajax and a kind of "observer"... But I don't know enough about Cake to plan this :) On the other hand, the domain in which I work does not imply different users access the same record, or seldom. Now, the current application does not care about this problem : the last who talks is right ! Anyway, no solution is perfect. > The other approach is to implement a "lock" mechanisms (I know it can > be quite complex, mainly if the user shut down the computer etc ..but > can be handled), to avoid other people being able to get a record for > modifying when someone else can possibly modify it before you do ... > > A part from this, I did not try your solution, but seems to handle the > case, maybe a bit costive thought. Using the security component can > avoid people to post after a certain time .. a way to explore ... > > I will use session with a timeout anyway. It may help. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
