Scott M Stark wrote:
> A JMX microkernel on the client is an avenue to explore. The focus
> should be extending the current dynamic proxy and detached invokers
> to a kernel for peer-peer type of computing: agents, grid computing,
> JMS, RMI callbacks, distributed caches, and whatever P2P is going by
> these days.

As always Scott is 10 (two ;) steps ahead of me.

> To me the extension is one of a client simply downloading smart
> proxies to downloading a microkernel whose base configuration is
> defined by the server, extensible by the client, and capable of
> offering services for peer-peer computing.

+1. This all came about because I was thinking about client side caches with server invalidation. Without the JMX kernel it is a pain because we have invent a totally new architecture to handle server to client invocations. If we have the kernel, we quickly prototype this by reusing the server invokers. Of course our existing invokers won't work for a real deployment with clients behind a firewall, but it is a good start.

-dain



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to