[jboss-dev-forums] [Design of POJO Server] - Re: Controlling deployments via a barrier bean

[adrian@jboss.org]

OFF TOPIC, but on a related issue. 

I said a while ago that a real profile service implementation
has a lot in common with JBoss Cache (at least in terms of aspects/technology if
not in implementation :-).

It is a (possibly transacted/distributed) tree like structure with an
abitrary backing store which should be able to scale from standalone to 
clustered environments.

Similarly it has requirements to track fine grained changes inside the tree
(changes to the items of metadata - the fields on the managed properties) 
and applying them atomically.

Some areas where it differs are that the (sub-)profile is versioned as a whole.
Related to this is that the distribution of the changes has a slightly different
semantic in that changes to the metadata would first be tried locally
or on some staging cluster before distributing the new version across the 
production cluster.

There are other parts that are not related to the cache structure, e.g. retrieving statistics
or invoking managed operations like flushing a pool, but these have more
in common with jgroups clustered invocation sematics.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154474#4154474

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154474