[xwiki-devs] [VOTE] Move remote observation manager from sandbox to core
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) Here is my +1 -- Thomas Mortagne
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]> 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 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
-- Thomas Mortagne
-- Thomas Mortagne
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]
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? 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
On Tue, Aug 11, 2009 at 18:02, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]
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?
ROM job is to do the communication between OM and the network so yes it's using OM api.
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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Aug 11, 2009, at 6:15 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:02, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]
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?
ROM job is to do the communication between OM and the network so yes it's using OM api.
ok I didn't mean using the api but implementing it. -Vincent
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
On Tue, Aug 11, 2009 at 18:18, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 6:15 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:02, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]
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?
ROM job is to do the communication between OM and the network so yes it's using OM api.
ok I didn't mean using the api but implementing it.
You can see ROM itself has a two way automatic conversion/communication tools between OM and JGroups.
-Vincent
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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Tue, Aug 11, 2009 at 18:02, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 5:41 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 17:33, Thomas Mortagne<[email protected]
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?
Ok for me (I don't like that much changing something to change re-change it after but if xwiki-core-observation is reserved for the parent we need to rename it)
Is the remote code using the api from observation or not?
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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
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. +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
On Tue, Aug 11, 2009 at 18:00, Vincent Massol<[email protected]> 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.
+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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Aug 11, 2009, at 6:11 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:00, Vincent Massol<[email protected]> 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? Thanks -Vincent
+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
On Tue, Aug 11, 2009 at 18:19, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 6:11 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:00, Vincent Massol<[email protected]> 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?
It does not generate text it generate Serializable event/source/data.
Thanks -Vincent
+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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On Aug 11, 2009, at 6:23 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:19, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 6:11 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:00, Vincent Massol<[email protected]> 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?
It does not generate text it generate Serializable event/source/data.
SerializableEventFactory |- SerializableEvent createSerializableEvent(Event) ? -Vincent
+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
On Tue, Aug 11, 2009 at 18:27, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 6:23 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:19, Vincent Massol<[email protected]> wrote:
On Aug 11, 2009, at 6:11 PM, Thomas Mortagne wrote:
On Tue, Aug 11, 2009 at 18:00, Vincent Massol<[email protected]> 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?
It does not generate text it generate Serializable event/source/data.
SerializableEventFactory |- SerializableEvent createSerializableEvent(Event)
?
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.
-Vincent
+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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 About modules naming my preference goes to: |_ xwiki-observation-manager |__ xwiki-observation-manager-local |__ xwiki-observation-manager-remote On Tue, Aug 11, 2009 at 5:33 PM, Thomas Mortagne<[email protected]> 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)
Here is my +1
-- Thomas Mortagne _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+0 Thanks, Marius 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). - 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
participants (4)
-
Jean-Vincent Drean -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol