Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Riena » How to implement Remote Observer Pattern with Riena?
How to implement Remote Observer Pattern with Riena? [message #646768] Thu, 30 December 2010 20:57 Go to next message
Hendy Irawan is currently offline Hendy Irawan
Messages: 58
Registered: July 2009
Location: Bandung, Indonesia
Member

Examples I've seen above Riena OSGi services seem to involve only RPC
style calls.

Is it possible to implement Remote Observer pattern, especially
asynchronously? i.e. register the client object(s) as an observer of an
observable object on the server. And when the server want to update the
client, it triggers the observer(s) method, potentially asynchronously
/ non-blocking.

Here's an example of how I did it with Apache Camel:
http://spring-java-ee.blogspot.com/2010/01/advanced-event-no tification-
framework.html

but I'm not sure about Riena.

Thank you.

--
Eclipse Driven Rich Application Development -
http://eclipsedriven.blogspot.com/
Re: How to implement Remote Observer Pattern with Riena? [message #648387 is a reply to message #646768] Wed, 12 January 2011 16:28 Go to previous message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Am 30.12.10 21:57, schrieb Hendy Irawan:
> Examples I've seen above Riena OSGi services seem to involve only RPC
> style calls.
>
> Is it possible to implement Remote Observer pattern, especially
> asynchronously? i.e. register the client object(s) as an observer of an
> observable object on the server. And when the server want to update the
> client, it triggers the observer(s) method, potentially asynchronously
> / non-blocking.
>
> Here's an example of how I did it with Apache Camel:
> http://spring-java-ee.blogspot.com/2010/01/advanced-event-no tification-
> framework.html
>
> but I'm not sure about Riena.
>
> Thank you.

Riena currently only supports making RPC calls. There is no remote event mechanism. Also the server is usually stateless
which means that no object held for a user on the server. Therefore there is no object that can be observed. The
advantage and reason is that it make the system very scaleable since every RPC call can be answered by a different
server instance.

Maybe the current implemented mechanism can be extended, or you implement a new remote service provider for Camel or
just directly use the Riena UI with the Apache Camel implementation you wrote.

hope that helps, if not let me know

christian
Previous Topic:Riena Security - Session is null at some calls
Next Topic:Riena on Ubuntu 10.10
Goto Forum:
  


Current Time: Tue Sep 23 04:37:31 GMT 2014

Powered by FUDForum. Page generated in 0.01664 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software