Ideally you should do this on server side and not from Flex. Keep version number of every record. Every time a record is updated version number is increased. Send the version number from client to server and vice-versa. Before updating on server check if the version number in DB is greater than the one from client. If yes, it means somebody has already updated the record. Show appropriate message.
On Flex side I am not sure how can you check the concurrent actions. Because how do you share information across client instances? You can look into "LocalConnection" in flex but then it be very tedious to maintain such kind of thing on client. Rgds, Ashish On Fri, Jun 25, 2010 at 12:48 AM, Flexitechy <[email protected]> wrote: > Friends, > > How can i handle concurrency in flex? Let me explain : I have > a flex application something like employee management system. One > person is adding some employees to the system, at the same time second > person is adding some other employees or deleting an employee. I want > to indicate the second person regarding the changes made by first > person and vice versa... > > Thanks, > lalk > > -- > You received this message because you are subscribed to the Google Groups > "Flex India Community" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<flex_india%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/flex_india?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Flex India Community" 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/flex_india?hl=en.
