I created the same scenario using terracotta, see terracotta.org. Terracotta makes from several vm's (in your case the desktop app and the web server, eg tomcat) seem as one. There is not a specific programming model to be learned, it's just Java (TM).
So you can use the event listeners on your beans to be notified of changes in data by the browser. Terracotta syncs the data transparently between the vm's. KlaasJan On Aug 18, 11:02 pm, jahid <[email protected]> wrote: > Thanks for the suggestion, I will look into it. But here the important > thing is, the communication is initiated by the browser, and then the > client just continues. Otherwise client have no clue when to start > communication. As I said, I do not know if xmpp takes care of that. > But I will definitely look into it. Thanks one more time. > > On Aug 18, 10:56 pm, pforhan <[email protected]> wrote: > > > > > I'd recommend a Jabber (XMPP) solution -- most often used as a chat > > protocol, it has a lot of flexibility, and it's great for this kind of > > direct communication. Smack is a well-known Java implementation. > > There seem to be several projects out there that offer AJAX to XMPP > > bindings, which could handle the browser end of things... > > > Pat. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
