I don't have a clear picture of what you're trying to accomplish. That said...
If you're responding to Jabber server events and then propogating them to Jabber clients, then cut out the middleman (SQL db) by writing a Jabber module or component and then stream the events straight to the clients. If you're caching/summarizing information and storing it in a db, then you can still write a Jabber module or component to reap the data. On the flip side, write another module or client to detect when your flash client comes online and then send them the data via XMPP. Try to adhere to the old truism of keeping moving parts to a minimum. I'm also not a big fan of scrounging through logs to guesstimate what's going on. Especially when Jabber has such a nice mechanism for gaining access to the raw XML packets (or am I supposed to say stanza :) Hope that helps, Mike > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Carlos Castellanos > Sent: Wednesday, July 09, 2003 12:25 PM > To: [EMAIL PROTECTED] > Subject: [JDEV] Java/XML > > > Hi all, I have a question regarding a java-based application > that I am building. I am using a java servlet to > periodically check server logs for new entries, parse this > data and write it to a database. I then want to send this > data (everytime the database is updated) to a Flash-based > client (which can read XML via the XMLSocket object). > > My question is: Should/Could I use jabber to send the XML > streams from the db (via xdb_sql) or am i better off > generating the xml with java (and forgetting about jabber altogether)? > > thanks, > Carlos > > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
