Paul,
So would the right place to export an Object
from an API standpoint be :
AltrmiFactory.exposeObject(Object o);
?
Regards,
Vinay
--- Paul Hammant [EMAIL PROTECTED] wrote:
Vinay,
Yes you are right BEEP looks better. There is a BSD
impl on SF :-
Vinay,
Paul,
So would the right place to export an Object
from an API standpoint be :
AltrmiFactory.exposeObject(Object o);
You mean in the context of BEEP and the layer it represents inside AltRMI ?
I don't quite understand what you are asking here
AltrmiFactory is a client-side class,
Vinay,
Paul,
I was aiming along the lines
of UnicastRemoteObject.exportObject(Remote obj) .
For the EventNotifier example I was trying
to come with ,
the Subscriber exports itself
and passes the reference of it to the Server.
Subscriber:
// SubscriberInterface.java
public interface
Hey dude, you're scaring me with RMI interfaces!
Sorry not my intention but somehow couldn't
stop thinking of this example over Altrmi
without much of an modification...
Pub/Sub is just an fancy name for callbacks not so?
Are we not talking
about the same thing?
We are ...
Maybe I
Vinay,
Yes you are right BEEP looks better. There is a BSD impl on SF :-
http://sourceforge.net/projects/beepcore-java/
I don't think it is an issue for Request/Reply as it is a layer between
AltrmiInvocationHandler and the true streaming mechanism...
- Paul
Hi,
dghmux seems kewl,
However
