hi all;
in my application an HTTP request potentially updates multiple backend
devices. the number of devices can vary between 5 and 100.
for the end user, the update has to be in a synchronous nature for the user
expects to view his update data as a part of the next page.
the protocol used between the app server and the devices is not decided upon
yet. main options are XML over some transport or JDBC to a DB on the device.
there are many doubts around here about the capability of the app server to
handle the large amount of devices. for example, say i want to use JDBC.
connecting to 100 databases seems like something that will crash the app
server. having 100 connection pools also seems unreasonable.

i am looking for suggestions, best practices, of ways to 'attack' this
issue.
any suggestions, similar experiences, related patterns would be very
helpfull.

thanks in advance.

____________________
Guy Katz
Allot Communications
gkatz@(protected)
tel: +972 9 7619288
fax: +972 9 7443626

====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)