11 Aug
2009
11 Aug
'09
6:40 p.m.
On Tue, Aug 11, 2009 at 18:27, Vincent Massol<vincent(a)massol.net> wrote:
On Aug 11, 2009, at 6:23 PM, Thomas Mortagne wrote:
No it need event/source/data (LocalEvent) to fill a proper RemoteEvent
which is serializable, i can't convert event, source and data totally
separately since it could need the whole thing to decide what to put
where and what is not required, i prefer to give theses all the
informations and let it fill the RemoteEvent the way it wants it to
be, it can even decide that the event should not be send (for example
for view document events). I tough of this factory but latter as a
tools provided to the converters to convert common data types.
On Tue, Aug 11, 2009 at 18:19, Vincent
Massol<vincent(a)massol.net>
wrote:
SerializableEventFactory
|- SerializableEvent createSerializableEvent(Event)
?
On Aug 11, 2009, at 6:11 PM, Thomas Mortagne wrote:
It does not generate text it generate Serializable event/source/data. On Tue, Aug 11, 2009 at 18:00, Vincent
Massol<vincent(a)massol.net>
wrote:
>
> On Aug 11, 2009, at 5:33 PM, Thomas Mortagne 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).
>
> I don't fully understand what EventConverter is and how it fits in
> the
> OM.
This is not for OM it's for ROM as i said we want to convert events
before sending them to the network. First we don't want to send the
whole XWikiDocument and XWikiContext and second we can't since
XWikiDocument is not Serializable so ROM has so id how to send it to
the network.
ok so it's actually a Serializer isn't it? It's used to serialize
events so that they can be sent over the network.
EventSerializer?
-Vincent
--
Thomas Mortagne
>>> +1 for the rest even though I
haven't reviewed the code yet.
>>>
>>> Thanks
>>> -Vincent
>>>
>>>> - 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)
>>>>
>>>> Here is my +1
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs