28 May
2013
28 May
'13
10:05 a.m.
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.
Yes there are two objectives
- first offering a remote API to get results of queries from light clients
- how can we build light clients
So I would like the data sent around to be described so that for example we have the list
of messages that we can apply to the data on the client to
continue the flow of interaction.
Doru what we should think is do we want to filter messages that we want to expose to
client.
Stef
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:
Excellent! Welcome Vincent
Alexandre
On 24 May 2013, at 05:19, Vincent BLONDEAU <vincent.blondeau(a)polytech-lille.net>
wrote:
--
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 Hello,
I’m doing an internship in the INRIA team RMod for 3 month. During this internship, I
would like to export Moose on the web.
I know there is a REST library on Seaside and we would to use it.
Have you got some pointers or links on resources that I can use to doing this ?
Thanks
Vincent BLONDEAU
Student in Software Engineering and Statistics
Polytech Lille
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev