first, great job paul! the phoenix blocks and app listener made it super-easy 
to plug into the phoenix side of my application.

i'm wondering how to best handle the client side (currently cocoon2). I am 
going to use the SocketObjectStreamSubscriber just by adding it as a 
component to cocoon. I'm curious as to its thread safety and its intended 
general usage pattern. 

Since it is designed to be a phoenix block, I'm guessing that it will be okay 
to subclass and make ThreadSafe so the ECM in cocoon treats it right?

How about usage then? I was just going to do lookup()'s, but what about 
calling close() in such an environment, should close() only be called when 
the component is shutting down (ie also implement Startable and call it in 
the stop() method)?

I haven't actually gotten to the point of *running* with the altrmi stuff, 
still retrofitting my code.
-pete

-- 
peter royal -> [EMAIL PROTECTED]

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to