1. Use synchronization with the synchronized keyword
2. Since a server cannot open an http port to the remote client, I don't
think HTTP can be used from the server side to notify client of changes.
Client would have to either:
a. Use polling, by making http requests every so often
b. Use persistent socket connection to the server
c. Use "open" http request strategy to always keep an http request
outstanding
-AP_
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Santosh Kumar
Sent: Tuesday, May 08, 2001 8:17 AM
To: Orion-Interest
Subject: Simple Java Doubts
Question 1:
How does an elementary Singleton pattern based Object behave
in a multi-threaded environment? What is this phenomenon called? How do you
make such a Singleton Object thread safe?
Question 2: What are the two methods typically employed to notify remote
clients distributed over the Internet of events that take place on a
central server? Like changes in the price of options, market depth, or an
order
execution? What are the relative advantages/disadvantages of each of
these strategies? Specifically, how can they be implemented in Java to
allow
for firewall tunneling over HTTP?
