William,
Why don't you educate me?
From my understanding, the primary difference between T3 and JRMP (and the
primary reason for WebLogic creating T3) is that T3 supports multiplexing
of concurrent requests across a single socket (for all remote objects
living in the same remote JVM) as opposed to JRMP which uses multiple
sockets. Therefore, the wire format of the entire message (e.g., the
request must include some information about the target of the invocation
since the target object's skeleton is not the one processing the request on
the other end of the socket) and the handshaking must be different for T3
and JRMP.
However, in order to send an RMI request across a socket, some object(s)
must be serialized into a series of bytes (granted, the object(s)
representing the request are almost certainly different for T3 vs.
JRMP). My question was how do you know that when constructing an RMI
request to be sent using the T3 protocol that WLS is not serializing the
objects using the standard Java serialization mechanism to flatten the
objects into a series of bytes? And if you know this to be true, why is it
important since the objects are re-materialized before any client code ever
sees them? How is this any different than the situation with products that
use IIOP instead of JRMP (i.e., one that uses IIOP to pass the objects
across the network and Java serialization to write it to local disk)?
Thanks,
Robert
At 05:43 AM 3/9/00 -0500, you wrote:
>Robert,
>
>Sun's serialization is a fat as you can get it to be. Please do more
>research.
>
>William
>
> > -----Original Message-----
> > From: Robert Patrick [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, March 08, 2000 6:00 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: sharing a Session Bean
> >
> > At 10:16 AM 3/4/00 -0500, Laird Nelson wrote:
> > >"Louth, William (Exchange)" wrote:
> > > > Why not use a stateless session bean? I know that Web Logic has very
> > > strange
> > > > behavior when it comes to serialization. When sending over the wire
> > > they use
> > > > their T3 version and when passivating they use sun's serialization.
> > >
> > >Can't they do this? Clients shouldn't care, right?
> >
> > And since T3 is the WebLogic RMI implementation's wire protocol
> > (comparable
> > to Sun's JRMP), how do you know that WebLogic doesn't use standard Java
> > serialization to flatten objects that are passed in a T3 message?
> >
> > Robert
> >
> > ==========================================================================
> > =
> > 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".
===========================================================================
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".
