On 15 avr. 08, at 11:23, Vincent Massol wrote: > >> The only thing I propose to put in it (at least for the moment) is >> the >> swizzle replacement Fabio wrote, a standalone library containing both >> xwiki xmlrpc model and client code (like swizzle). > > I think I don't understand what you're proposing. > > More specifically why do you want to introduce a xwiki-commons > directory? > > Why not create: > > xwiki-platform-core/xwiki-xmlrpc/ > |_ xwiki-xmlrpc-model/ > |_ xwiki-xmlrpc-client/ > > And then in the future when we move the server part it can go in > xwiki- > xmlrpc-server/? > The reason why I wrote only one module is that the 95% of the code in this module is shared and there is only one class that is not used by both the client and the server, namely the XWikiXmlRpcClient (which is used, of course, only by the client).
So I thought that creating a module for just one class was a bit overkill. It was some kind of module-proliferation optimization :) However, the solution you mentioned is better from the logical point of view, and makes even more sense if we think of a future xwiki- xmlrpc-server that, if I am not wrong, would incorporate the current xmlprc logic as a separate (plexus?) plugin. > note: I assumed the model is used by both the client and the server > That's correct. Thanks, Fabio _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
