Using XML for configuration files makes good sense. It also makes good sense
to use the standard JAXP API for parsing it.

On the other hand, parsing and writing the configuration files is all
internal to the router, so really you are free to use whatever XML parser
you choose. Take a look at Electric XML at http://www.themindelectric.com
for a very small, very fast parser. One thing I like about SwiftMQ is that
it is small, so I hope that adding XML doesn't cause it to bloat.

David A. King
Intel Corp.


-----Original Message-----
From: Scott Smith [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 22, 2001 11:10 AM
To: [EMAIL PROTECTED]
Subject: [developers] props -> xml


I love it.  It would be a huge improvement.  I am a huge advocate of XML
(where it's appropriate).  It does complicate the deployment process though.
Be sure to use the JAXP API to perform all XML operations and you might want
to make two distributions: one which includes an XML parser, and one that
assumes there is a JAXP compliant parser available.  

Scott

> -----Original Message-----
> From: Andreas Mueller [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, May 22, 2001 12:22 PM
> To: [EMAIL PROTECTED]
> Subject: [developers] props -> xml
> 
> 
> Hello,
> 
> [don't beat me]
> 
> we like to change the property format of the router config to XML in 
> future (end of the year or so). XML has some important 
> advantages. For 
> example, instead of writing
> 
> sys$queuemanager.queues.names=q1,q2,q3
> 
> you will have something like this
> 
> <queuemanager name="sys$queuemanager" class="...">
>   <queue name="q1" cachesize="500" />
>   <queue name="q2" cachesize="500" />
>   <queue name="q3" cachesize="500" />
> </queuemanager>
> 
> We can also use XML Schemas to validate the XML and we will 
> have a generic 
> approach then to be used for the Swiftlet API.
> 
> The disadvantage is that you have to learn the new format and 
> we have to 
> re-write our documentation and have to change the code (also for the 
> extension Swiftlets). We will provide a converter props->XML, 
> of course.
> 
> What are your opinions?
> 
> -- 
> Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
> SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
> 
> 
> ------------------------------------------------------
> SwiftMQ developers mailing list * http://www.swiftmq.com
> To unsubscribe from this list, send an eMail to 
> [EMAIL PROTECTED] and write in the body of your message:
> UNSUBSCRIBE developers <your-email-address>
> Archive: http://www.mail-archive.com/developers@mail.iit.de/
> 
> 
> 
> 

------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to 
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/


------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to 
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/developers@mail.iit.de/




Reply via email to