11 Aug
2009
11 Aug
'09
6:20 p.m.
On Tue, Aug 11, 2009 at 18:18, Vincent Massol<vincent(a)massol.net> wrote:
On Aug 11, 2009, at 6:15 PM, Thomas Mortagne wrote:
You can see ROM itself has a two way automatic
conversion/communication tools between OM and JGroups.
On Tue, Aug 11, 2009 at 18:02, Vincent
Massol<vincent(a)massol.net>
wrote:
ok I didn't mean using the api but implementing it.
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
ROM job is to do the communication between OM and the network so yes
it's using OM api. On Tue, Aug 11, 2009 at 17:33, Thomas
Mortagne<thomas.mortagne(a)xwiki.com
> wrote:
> Hi devs,
>
> I would like to introduce a first partial beta of the event network
> distribution system in the 2.0M3.
>
> Note that the module itself is complete what will need to be done
> with
> debugging is making everything in core use the new Observation
> Manager
> instead of the old notification service.
>
> For this release i plan to:
> - add the remote observation manager module (disabled by default)
> - implement a EventConverter for documents events (event convert
> has a
> generic converter for Serializables events but documents converted
> has
> XWikiDocument and XWikiContext we want to filter before sending
> it to
> the network).
> - make XWiki cache store listen to remote doc event to invalidate
> the
> cache accordingly (this is the main thing that will bring event
> based
> clustering support to XWiki, all the rest is already supposed to
> update its cache based on events remote or not)
I also need to reorg a little maven project to have current
observation and remote observation as sub modules of an observation
parent.
* xwiki-core-observation-parent
* xwiki-core-observation
* xwiki-core-observation-remote
I'd much prefer to use xwiki-core-observation as the parent (as we're
doing in lots of places already).
I think using parent is bad practice we have in a few places.
You could name the module xwiki-core-observation-local or xwiki-core-
observation-api or xwiki-core-observation-default.
For future, -api + -local + -remote sound ideally balanced to me. So
maybe xwiki-core-observation-local is best?
Is the remote code using the api from observation or not?
-Vincent
--
Thomas Mortagne
> If not, then I guess default is better than
local for the other
> module.
>
> Thanks
> -Vincent
>
>>
>> For now and refactor xwiki-core-observation latter to cut it into
>> api/implementation but i would like to do the 2.0M3 release as
>> soon as
>> possible so better to not do it in a hurry so this can wait the RC.
>>
>>>
>>> Here is my +1
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs