The messages are stored centerally at the server.
Each conusmer has their own table/object which indicates the messages they have read.
At the time of connect, the consumer compares his own table with the master table.
The consumer (Flex app) begins loading the unread messages.
The read messges are updated at the consumer's server table.
That will be $4000 please.
Your reply is useful, but feasible I have to say. Creating DB tables, updating entries and synchronizing contents involve a lot of work. As we can use blazeDS and LCDS, that'll be good option. From online help, it doesn't explain what will happen if consumer disconnects temporarily which is very important to me. If some messages are missed, the whole process can't move on smoothly.
Simply speaking, I hope below issues can be solved with blazeDS or LCDS:
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 and regards,
Let us know how it goes