Tim,
I think XML and Java are a very powerful combination but I do feel very
uneasy in using in this context. I think if current clients are Java based
that it would seem a bit unwise to take the performance hit associated with
sending xml messages considering the current tagging mechanism. I supose you
could always compress the message but again you are creating a performance
hit where it is probably unwarranted. Before giving up on Java serialization
we should come up with reasons for the change.
I understand the reason for the swing group considering using xml in fact I
proposed this idea on the JBuilder newsgroup about a year ago before this
all came out. I previously worked with Delphi which was the basis for
JavaBeans and had seen something similar with the delphi .dfm files. My
thinking was that this was a way we could create a GUI in one tool and view
in another. This currently is not possible. Delphi separates the screen
structure and behavior, current Java ide's do not.
OK getting back... why not instead consider adding a layer into your
architecture which can publish XML messages constructed from the
details-like objects obtained from the normal Java client service layer. A
simple but powerful framework can be quickly built to support this - I have
been thinking about do something on this. My first thoughts on this
interesting post.
kind regards,
William Louth
> -----Original Message-----
> From: Tim Endres [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 28, 2000 2:32 PM
> To: [EMAIL PROTECTED]
> Subject: XML vs. Serial (was: Cached Rowsets-do we need to use them)
>
> > In fact we have considered using XML hierarchies instead of serialized
> objects, but haven't
> > made the transition because object methods provide us great flexibility
> in defining properties
> > for the client developers.
>
> Victor,
>
> Could you please elaborate. I for one, and I am sure more on this list,
> would
> like to know more about your decision to not move forward on the XML
> front.
>
> We are looking at this decision currently. Our system has a low enough
> volume
> that we are looking at XML for all data communication, as opposed to
> serialized
> objects.
>
> Any thoughts or experience you have on this topic would be most welcome.
>
> 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".
***********************************************************************
Bear Stearns is not responsible for any recommendation, solicitation,
offer or agreement or any information about any transaction, customer
account or account activity contained in this communication.
***********************************************************************
===========================================================================
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".
