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 SubscriberInterface
> extends java.rmi.Remote {
> void inform(Event event) throws
> java.rmi.RemoteException;
>}
>
Hey dude, you're scaring me with RMI interfaces!
>And ConcreteSubscriber does something like
>ConcreteSub()
>{
>UnicastRemoteObject.exportObject(this);
>}
>
>
>So what you are proposing with PropertyChangeListeners
>
It was just an example of a use of call-back.
>would also work in my scenario too since there I
>would be passing the PropertyChangeListener
>objs to the server rather than a custom
>Subscriber_stub.
>
>But this was the direction I was coming from ...
>
>comments.?
>
Publish/Subscriber heh? I think you know more about where you want to
go with this than I do.
Pub/Sub is just an fancy name for callbacks not so? Are we not talking
about the same thing?
- Paul
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
