It's exactly that ! I'll mail the seaside list. Thanks, Vincent -----Message d'origine----- De : moose-dev-bounces(a)iam.unibe.ch [mailto:moose-dev-bounces@iam.unibe.ch] De la part de Tudor Girba Envoyé : lundi 27 mai 2013 06:37 À : Moose-related development Objet : [Moose-dev] Re: Moose on the web Hi Vincent, Welcome, indeed! :) If I understand correctly, you would like to have more of a "remote Moose server", and not necessarily the rendering associated with it. And in order to communicate with the server you would like to use a REST API. And for this to happen, you would like to use the Seaside REST API. Is that correct? If yes, I believe the best place to get more answers about the technical aspects is on the seaside mailing list. Cheers, Doru On May 27, 2013, at 2:42 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: <vincent.blondeau(a)polytech-lille.net> wrote: internship, I would like to export Moose on the web. this ? -- www.tudorgirba.com "Be rather willing to give than demanding to get." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Mon, May 27, 2013 at 10:31 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: +1

On Mon, May 27, 2013 at 6:36 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: Yes. Glamour-seaside already does the rendering of Moose entities, its probably general-purpose, in the sense that its not related to Moose, but we have an infrastructure for rendering Moose entities on the web. The idea of this project is to be able to query server for models, take a model and query its elements and their links/associations. There are some questions around the "server" notion that Vincent will work on, e.g. - Do we need to associate an "ID" to search for an entity in the model or the names are unique in a model (I dont think so). - Should the client be provided with the data it asked for, or can we introduce a certain notion of meta-data so that the client knows the entities and messages that can be sent to the entities it received. - ensure that different data formats (principally, JSON and then probably XML) can be communicated to the client. - not to clutter the network, be able to ask a certain number of Moose entities. I am not aware of all the efforts made in the past to support such type of approach in Moose. Did someone already work on this? For the project, we'll do some small iterations and share the results for you to test:-). Usman And in order to communicate with the server you would like to use a REST