> The problem I have with CORBA (and as I'm just beginning to
> examine EJB) are firewalls, firewalls, firewalls. It looks like to me
> as long as you control the firewalls where the corba connections
> pass, you can have good success. If you don't, your just begging
> for problems. With XML the firewalls are barely a hiccup.
Tom,
Thanks for the post.
I wanted to follow up and say that firewalls can be dealt with in our
particular case, since our client will not be using CORBA. We can use
Serialization by utilizing the same technique of pushing the serialized
objects through an HTTP POST mechanism, where the URL's pathInfo selects
the Class/Method required, or it is all bundled into a "Request" object
which defines the Class/Method. So firewalls do not preempt Serialization.
I realize that I am going to incur a performance hit using XML, but I
believe that we can afford it.
One of the compelling arguments for XML is that I can then have virtually
any client - Java, Perl, C, C++, Python - as long as the can generate and
parse the XML.
I also feel it makes debugging the commlink easier, due to its readability,
although this is not a major consideration.
The problem with Serialization, from our point of view, is versioning. We
have found it to be an extra maintenance cost to manage the different
versions of the objects used, whereas the XML seems a little more flexible.
I just ran some tests with Sun's JDK1.1.8, a Pentium II 450 W2K box, and
using Apache's Xalan and Xerces packages. Very preliminary tests show that
I can parse very simple XML documents to the tune of 1000 per 6 seconds.
And for XML/XSLT, I can able to translate the simplest of documents to the
tune of 1000 per 12 seconds. The numbers fall within our requirements, but
I doubt they will be sufficient for all projects. And I still do not have
any numbers of memory consumption.
tim.
Tim Endres [EMAIL PROTECTED]
ICE Engineering, Inc. http://www.trustice.com/
"USENET - a slow moving self parody." - Peter Honeyman
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
