Is in't this the case similar to implementing a singleton in EJB(which ofcoarse is n't viable)
 
I see the situation like this
    1-we need multiple access to the same instance
    2-all the instances (on different VM's) should look a like
    3-provide fault tolerance(use replication)
    4-provide persistance(but not using database)
 
One possible solution looks like this
    -use a CORBA Singleton server, that does the job of maintaing only one instance of the chat text.(first, second and third will be solved)
    -use a statefull session bean from the CORBA Singleton server so this statefull session bean would maintain the state of the current text.( fourth problem will be solved)
 
Am i going too far to achieve what you require -I am not sure
 
Sesh
 
 

Reply via email to