Hi Felix, Producer, consumer are just a messaging channel like chat, 1. You can add acknowledgement to find whether the message was properly delivered. 2. In case of message not delivered, push it to an RSS feed (again DB is required), and mark the entry as read after it is listened.
Regards, Devaraj On Jul 13, 1:52 pm, Felix <yancao...@gmail.com> wrote: > Hi all, > > As a frontend solution, Flex is really powerful and fascinate. On the > other hand, it inevitiably needs to exchange data. And I am trying to > find a good way to build a stable and reliable application. > > Here's the workaround. On server side, blazeDS or LCDS is involved and > on frontend component Consumer and Producer are used to interact. A > group of users cooperates on the whole processing. Everybody will send > an update once he finished current job. > > I don't want to do business with database because creating DB tables, > updating entries and synchronizing contents involve a lot of work. > BlazeDS is my current option, but online-help doesn't explain what > will happen if consumer disconnects temporarily. If some messages are > missed, the whole process will go into mess. > > Simply speaking, I hope below issues can be solved: > 1) how to ensure messages are delivered to subscribed consumers if > they are temporarily disconnected? > 2) how to recover work if consumers are thoroughly disconnect? > > Thanks a lot, > Felix > > Thanks and regards, > > Felix --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Flex India Community" group. To post to this group, send email to flex_india@googlegroups.com To unsubscribe from this group, send email to flex_india+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/flex_india?hl=en -~----------~----~----~----~------~----~------~--~---