everything in WebLogic is in-process. this may or may not change due to the
ejb1.1 spec that precludes intra-vm tuning of rmi. in any case, your
concerns are 100% valid, but i'd recommend against session/flyweight (see
discussion on this topic the last few days)
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, May 20, 1999 12:52 AM
> To: [EMAIL PROTECTED]
> Subject: Call optimization within container
>
> Does anyone know how different containers (I'm especially interested in
> Tengah and IBM WebSphere) optimize calls between EJB's living in the same
> container (or even same VM)? I guess that this has some effect on design.
> For example isn't it a performance issue to use session-bean wrapping on
> entity-beans if calls between session-beans and entity-beans are not
> optimized (I would guess that in most cases session and entity-beans live
> in
> the same container). If calls are not optimized isn't it a better idea to
> go
> for Flyweight and use just session-beans?
>
> Jouni Juutinen
>
> ==========================================================================
> =
> 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".
