I
have a question for the brilliant minds.
I
have a project coming up that will require java applets as clients running in
or outside of a browser..these applets will need to
communicate with a server process for synchronizing each clients UI
components and to process URL calls to ASP pages running
on
another server on a separate machine. My question is this : My desired
implementation is to use a web services interface like
Apache Soap running on Apache/Tomcat and use the soap-servlet approach
to gateway all the requests to a object(s) that will
do
the actual work of updating a calling client and storing state for all
the associated clients. I'm concerned there could be some
performance issues with this type of implementation.? There could be
heavy interaction that needs to be stored to the server as
often
as
once every few seconds for each client..only text will be passed to and
fro..
and
also perhaps I'm missing an easier design for this...
Any
ideas..?
Thanks for any comments
JD
Great !
Which JVM is shipped with the watch
?
Have the new classes "HulkPunch" and "HulkRoar" already been
implemented ?
;-)
---
You are currently
subscribed to jdjlist as: [EMAIL PROTECTED]
To unsubscribe send
a blank email to
[EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
---
You are currently subscribed to jdjlist as:
[EMAIL PROTECTED]
To unsubscribe send a blank email to
[EMAIL PROTECTED]
http://www.sys-con.com/fusetalk
---