Hi, the current status port events server dual purpose in being human and machine readable. While XML messages might be a little easier to parse they would duplicate something we need to have human readable as well. Since its not too difficult to parse the current staus port messages (and we have the issue of maintaining compatiblity) I'd say it's not a much needed feature. BTW: The devlopers list would be a better place for things like this. Regards, Jan Frank Fischer wrote: > Hi > > I'm doing some development using the Status Port and just thought that > it might be a smart feature if we could have a Status Port that does > not just write out simple text lines but would use xml objects > instead. Of course communication would slow down a little bit, but > since in most cases an application using the Status Port will reside > on the same machine as the Gatekeeper, this wouldn't be a critical > issue. The advantage of a XML approach i think would be a very smart > way to handle events (means commands, information, and so on) and > would make the Status Port more less proprietary. > > What do the gnugk developers think about that? > > Greetings > Frank -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.willamowius.de/ ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
