RE: Antwort: RE: Antwort: String to SVGElement?

[Bishop, Michael W. CONTR J9C880]

Well it’s being integrated into an XMPP client, so XMPP must be the transport mechanism.  We’re designing a standard for whiteboarding that we hope to submit as a JEP (Jabber Extension Protocol).  I think you’re right overall though; I may need to come up with a structure to tell the client how to build the XML rather than send it as a String.  If it’s not as easy as I envisioned, I’m becoming more and more convinced that it needs to change.   Michael Bishop   From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, March 13, 2006 2:17 PM To: batik-users@xmlgraphics.apache.org Subject: Antwort: RE: Antwort: String to SVGElement?   When the elements are 'flat' (no child-elements), i would invent some java-structure, fill it, send it with RMI and use it on client-side to create the element. Hey - no need for flat elements - RMI can easily transfer object-trees. XML as the transfer-format _seems_ to an advantage, because there's a lot of XML and DOM around in the SVG-world. But thats an illusion: there may be support to serialize elements to XML-strings, but the reverse way requires quite much of a XML-parser. For me, XML is comfortable when I can use the integrated parser, tell him where the file is and have it transformed. dvholten