isn't what you asking very vendor dependent?
And somewhat less applicable to EJB and more with the Java2 Enterprise Edition?
Additional things to consider, the application interfaces and styles of communication.
(e.g. are your servers interactive, event driven, batch, etc...)
for #1, you could use JMS
fro #2, JSP or servlets
francis
"A mailing list for Enterprise JavaBeans development" <[EMAIL PROTECTED]>
wrote:
>Date: Mon, 6 Dec 1999 13:45:28 +0200
>I have a question on EJB performance over WAN, in two distinct scenarios:
>
>1. Server-to-server, over high capacity WAN links at both ends, and
>2. Browser-to-server, over a dial-up or low capacity link at the client end.
>
>Does anyone have experience regarding performance, reliability, and how
>bandwidth efficiency? Right now we are skeptical of EJB performance in both
>scenarios, and will probably use XML over Oracle Advanced Queuing for
>Scenario 1 and XML over HTTP for scenario 2. I am less than pleased with
>these solutions because of the large development overhead they incur.
>
>TIA,
>
>- Avi
>
>===========================================================================
>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".
--
The best thing about standards is that
there are so many to choose from.
===========================================================================
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".