Seaside and Rest

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside and Rest

Olivier Auverlot
For a new project, i need to make web services based into the Restful
architecture.My program must read, write, modify and delete informations
in a LDAP directory. I can do that with Perl... but i want to try to use
Pharo and Seaside :)

Someone has experience for this type of application ? How to manage the
HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.

Best regards
Olivier

www.auverlot.fr
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Runar Jordahl
Yes, you can use the ZincHTTPComponents. They will let you interface
to a REST interface.

Runar Jordahl

2011/2/11 Olivier Auverlot <[hidden email]>:

> For a new project, i need to make web services based into the Restful
> architecture.My program must read, write, modify and delete informations in
> a LDAP directory. I can do that with Perl... but i want to try to use Pharo
> and Seaside :)
>
> Someone has experience for this type of application ? How to manage the HTTP
> commands (PUT, GET, DELETE and POST) ? Thank you for your help.
>
> Best regards
> Olivier
>
> www.auverlot.fr
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Dale Henrichs
In reply to this post by Olivier Auverlot
Olivier,

Take a look at the Seaside-REST code in
http://www.squeaksource.com/Seaside30Addons.

With Seaside-REST you can switch cleanly back and forth between stateful
and RESTful requests and of course use Seaside facilities for
constructing your RESTful responses.

Dale

On 02/11/2011 05:36 AM, Olivier Auverlot wrote:

> For a new project, i need to make web services based into the Restful
> architecture.My program must read, write, modify and delete informations
> in a LDAP directory. I can do that with Perl... but i want to try to use
> Pharo and Seaside :)
>
> Someone has experience for this type of application ? How to manage the
> HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.
>
> Best regards
> Olivier
>
> www.auverlot.fr
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Philippe Marschall
2011/2/11 Dale Henrichs <[hidden email]>:
> Olivier,
>
> Take a look at the Seaside-REST code in
> http://www.squeaksource.com/Seaside30Addons.
>
> With Seaside-REST you can switch cleanly back and forth between stateful and
> RESTful requests and of course use Seaside facilities for constructing your
> RESTful responses.

Documentation is available at [1]

 [1] http://code.google.com/p/seaside/wiki/SeasideRest

Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Sven Van Caekenberghe
In reply to this post by Olivier Auverlot
Hi Olivier,

On 11 Feb 2011, at 14:36, Olivier Auverlot wrote:

> For a new project, i need to make web services based into the Restful architecture.My program must read, write, modify and delete informations in a LDAP directory. I can do that with Perl... but i want to try to use Pharo and Seaside :)
>
> Someone has experience for this type of application ? How to manage the HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.


Do you want to do client or server side or both ?

If you have a basic understanding of HTTP, the Zinc HTTP Components framework will help you get started very quickly. The code was written to be easy to understand and flexible to use. I have done both client and server REST interfaces on top of Zn.

There is also a nice Seaside addon framework (see Phillipe's reply). Building on top of Seaside it is both richer and heavier.

Sven

http://homepage.mac.com/svc/Zinc-HTTP-Components/index.html_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

NorbertHartl

On 11.02.2011, at 20:07, Sven Van Caekenberghe wrote:

> Hi Olivier,
>
> On 11 Feb 2011, at 14:36, Olivier Auverlot wrote:
>
>> For a new project, i need to make web services based into the Restful architecture.My program must read, write, modify and delete informations in a LDAP directory. I can do that with Perl... but i want to try to use Pharo and Seaside :)
>>
>> Someone has experience for this type of application ? How to manage the HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.
>
>
> Do you want to do client or server side or both ?
>
> If you have a basic understanding of HTTP, the Zinc HTTP Components framework will help you get started very quickly. The code was written to be easy to understand and flexible to use. I have done both client and server REST interfaces on top of Zn.
>
> There is also a nice Seaside addon framework (see Phillipe's reply). Building on top of Seaside it is both richer and heavier.
>
To me those two are completely separate. I love Seaside-REST and use it daily. Not having to care about routing of path/parameter combinations but just to write methods with pragmas is great. On the other hand Zinc gives a good access to the structure of HTTP messages. Phillipe not only did the Seaside-REST but also the seaside adapter for zinc. So in my case I want this two combined: Using zinc server as an adapter and Seaside-REST to control url access. Inside the seaside handlers you have again complete access to mime based strucure of entities created by zinc. My first tests using the combination of both was really impressive. And this approach is straight forward combinable with a seaside web application, too. A box full of wonderful tools.

my 2 cents,

Norbert

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

dtrussardi@tiscali.it
Hi,

A) i load Seaside-REST-Core-pmm.13 into Pharo image.

        I don't  found example to createRoutes.

        Any pointers would be greatly appreciated !

       

B) I an seaside application i used Paypal  to manage the pay online.

        Now i'm interested to manage the paypal service for Instan Pagament Notification or Express Checkout.

        I can manage this request with Rest support ?

        Any considerations about solve this problematic ?


        Anybody create interface for this service ?

        Thank,

                Dario


> On 11.02.2011, at 20:07, Sven Van Caekenberghe wrote:
>
>> Hi Olivier,
>>
>> On 11 Feb 2011, at 14:36, Olivier Auverlot wrote:
>>
>>> For a new project, i need to make web services based into the Restful architecture.My program must read, write, modify and delete informations in a LDAP directory. I can do that with Perl... but i want to try to use Pharo and Seaside :)
>>>
>>> Someone has experience for this type of application ? How to manage the HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.
>>
>>
>> Do you want to do client or server side or both ?
>>
>> If you have a basic understanding of HTTP, the Zinc HTTP Components framework will help you get started very quickly. The code was written to be easy to understand and flexible to use. I have done both client and server REST interfaces on top of Zn.
>>
>> There is also a nice Seaside addon framework (see Phillipe's reply). Building on top of Seaside it is both richer and heavier.
>>
> To me those two are completely separate. I love Seaside-REST and use it daily. Not having to care about routing of path/parameter combinations but just to write methods with pragmas is great. On the other hand Zinc gives a good access to the structure of HTTP messages. Phillipe not only did the Seaside-REST but also the seaside adapter for zinc. So in my case I want this two combined: Using zinc server as an adapter and Seaside-REST to control url access. Inside the seaside handlers you have again complete access to mime based strucure of entities created by zinc. My first tests using the combination of both was really impressive. And this approach is straight forward combinable with a seaside web application, too. A box full of wonderful tools.
>
> my 2 cents,
>
> Norbert
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

NorbertHartl

On 12.02.2011, at 14:22, [hidden email] wrote:

> Hi,
>
> A) i load Seaside-REST-Core-pmm.13 into Pharo image.
>
> I don't  found example to createRoutes.
>
> Any pointers would be greatly appreciated !
>
Have a look here: http://code.google.com/p/seaside/wiki/SeasideRest

>
>
> B) I an seaside application i used Paypal  to manage the pay online.
>
> Now i'm interested to manage the paypal service for Instan Pagament Notification or Express Checkout.
>
> I can manage this request with Rest support ?
>
> Any considerations about solve this problematic ?
>
Well, Seaside-REST is some kind of REST support but only for incoming requests as seaside itself is. It eases your way _providing_ RESTful stuff but not consuming RESTful stuff that is definitely application specific. Zinc components at least makes it easy to construct all kind of REST (in this case over HTTP) messages.

Norbert

>
> Anybody create interface for this service ?
>
> Thank,
>
> Dario
>
>
>> On 11.02.2011, at 20:07, Sven Van Caekenberghe wrote:
>>
>>> Hi Olivier,
>>>
>>> On 11 Feb 2011, at 14:36, Olivier Auverlot wrote:
>>>
>>>> For a new project, i need to make web services based into the Restful architecture.My program must read, write, modify and delete informations in a LDAP directory. I can do that with Perl... but i want to try to use Pharo and Seaside :)
>>>>
>>>> Someone has experience for this type of application ? How to manage the HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.
>>>
>>>
>>> Do you want to do client or server side or both ?
>>>
>>> If you have a basic understanding of HTTP, the Zinc HTTP Components framework will help you get started very quickly. The code was written to be easy to understand and flexible to use. I have done both client and server REST interfaces on top of Zn.
>>>
>>> There is also a nice Seaside addon framework (see Phillipe's reply). Building on top of Seaside it is both richer and heavier.
>>>
>> To me those two are completely separate. I love Seaside-REST and use it daily. Not having to care about routing of path/parameter combinations but just to write methods with pragmas is great. On the other hand Zinc gives a good access to the structure of HTTP messages. Phillipe not only did the Seaside-REST but also the seaside adapter for zinc. So in my case I want this two combined: Using zinc server as an adapter and Seaside-REST to control url access. Inside the seaside handlers you have again complete access to mime based strucure of entities created by zinc. My first tests using the combination of both was really impressive. And this approach is straight forward combinable with a seaside web application, too. A box full of wonderful tools.
>>
>> my 2 cents,
>>
>> Norbert
>>
>> _______________________________________________
>> seaside mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Olivier Auverlot
In reply to this post by Dale Henrichs
Thanks for the responses The community is very friendly :) It's cool for a newbie as me.

As I must use HTTPS for the connection to the REST services, I plan to use apache for the frontal webserver and Seaside/seaside-rest for the request processing.

I work now on a prototype for the test of the solution. Today, i downloaded Pharo 1.1.1 and installed Seaside. I selected WAComancheAdaptor on the port 8080/tcp. That runs perfectly.

In Montichello, I added a repository for seaside30addons and selected seaside-REST-core-pmm and seaside-test-Core. In the "test runner", I have 5 errors :

WAMime TypeStubHandlerTest>>#testMultipleConentTypeRouting
WAMime TypeStubHandlerTest>>#testSimpleAcceptRouting
WAMime TypeStubHandlerTest>>#testSimpleConentTypeRouting
WAPragmaBasedRestfullHandlerTest>>#testCreateRoutes
WAPragmaBaseRouteBuilderTest>>#testPlatformMethods

Must I add another components ?

Another little question : seaside-REST allows it to access to the DELETE and PUT commands of HTTP ?

thanks for your help.

Best regards
Olivier ;-)

www.auverlot.fr
Olivier,

Take a look at the Seaside-REST code in http://www.squeaksource.com/Seaside30Addons.

With Seaside-REST you can switch cleanly back and forth between stateful and RESTful requests and of course use Seaside facilities for constructing your RESTful responses.

Dale

On 02/11/2011 05:36 AM, Olivier Auverlot wrote:
For a new project, i need to make web services based into the Restful
architecture.My program must read, write, modify and delete informations
in a LDAP directory. I can do that with Perl... but i want to try to use
Pharo and Seaside :)

Someone has experience for this type of application ? How to manage the
HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.

Best regards
Olivier

www.auverlot.fr
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

sebastianconcept@gmail.co
tip: always maintain a copy of the script that brings you from A to B were:
A is a brand new laptop (where you can put a brand new pharo image) and
B is the latest code of your app running on it (including requisites)

for the rest don't worry, everybody is a noob at many many things (and a bit less noob at very very few things)

have fun





On Feb 15, 2011, at 11:21 AM, Olivier Auverlot wrote:

Thanks for the responses The community is very friendly :) It's cool for a newbie as me.

As I must use HTTPS for the connection to the REST services, I plan to use apache for the frontal webserver and Seaside/seaside-rest for the request processing.

I work now on a prototype for the test of the solution. Today, i downloaded Pharo 1.1.1 and installed Seaside. I selected WAComancheAdaptor on the port 8080/tcp. That runs perfectly.

In Montichello, I added a repository for seaside30addons and selected seaside-REST-core-pmm and seaside-test-Core. In the "test runner", I have 5 errors :

WAMime TypeStubHandlerTest>>#testMultipleConentTypeRouting
WAMime TypeStubHandlerTest>>#testSimpleAcceptRouting
WAMime TypeStubHandlerTest>>#testSimpleConentTypeRouting
WAPragmaBasedRestfullHandlerTest>>#testCreateRoutes
WAPragmaBaseRouteBuilderTest>>#testPlatformMethods

Must I add another components ?

Another little question : seaside-REST allows it to access to the DELETE and PUT commands of HTTP ?

thanks for your help.

Best regards
Olivier ;-)

www.auverlot.fr
Olivier,

Take a look at the Seaside-REST code in http://www.squeaksource.com/Seaside30Addons.

With Seaside-REST you can switch cleanly back and forth between stateful and RESTful requests and of course use Seaside facilities for constructing your RESTful responses.

Dale

On 02/11/2011 05:36 AM, Olivier Auverlot wrote:
For a new project, i need to make web services based into the Restful
architecture.My program must read, write, modify and delete informations
in a LDAP directory. I can do that with Perl... but i want to try to use
Pharo and Seaside :)

Someone has experience for this type of application ? How to manage the
HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.

Best regards
Olivier

www.auverlot.fr
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

NorbertHartl
In reply to this post by Olivier Auverlot

On 15.02.2011, at 14:21, Olivier Auverlot wrote:

Thanks for the responses The community is very friendly :) It's cool for a newbie as me.

As I must use HTTPS for the connection to the REST services, I plan to use apache for the frontal webserver and Seaside/seaside-rest for the request processing.

I work now on a prototype for the test of the solution. Today, i downloaded Pharo 1.1.1 and installed Seaside. I selected WAComancheAdaptor on the port 8080/tcp. That runs perfectly.

In Montichello, I added a repository for seaside30addons and selected seaside-REST-core-pmm and seaside-test-Core. In the "test runner", I have 5 errors :

WAMime TypeStubHandlerTest>>#testMultipleConentTypeRouting
WAMime TypeStubHandlerTest>>#testSimpleAcceptRouting
WAMime TypeStubHandlerTest>>#testSimpleConentTypeRouting
WAPragmaBasedRestfullHandlerTest>>#testCreateRoutes
WAPragmaBaseRouteBuilderTest>>#testPlatformMethods

Must I add another components ?

You need to load Seaside-Pharo-REST-Core as well.

Another little question : seaside-REST allows it to access to the DELETE and PUT commands of HTTP ?

yes.

Norbert

www.auverlot.fr
Olivier,

Take a look at the Seaside-REST code in http://www.squeaksource.com/Seaside30Addons.

With Seaside-REST you can switch cleanly back and forth between stateful and RESTful requests and of course use Seaside facilities for constructing your RESTful responses.

Dale

On 02/11/2011 05:36 AM, Olivier Auverlot wrote:
For a new project, i need to make web services based into the Restful
architecture.My program must read, write, modify and delete informations
in a LDAP directory. I can do that with Perl... but i want to try to use
Pharo and Seaside :)

Someone has experience for this type of application ? How to manage the
HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.

Best regards
Olivier

www.auverlot.fr
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: Seaside and Rest

Olivier Auverlot
It seems ok. All the tests are now green.

Thank
Olivier ;-)

www.auverlot.fr

On 15.02.2011, at 14:21, Olivier Auverlot wrote:

Thanks for the responses The community is very friendly :) It's cool for a newbie as me.

As I must use HTTPS for the connection to the REST services, I plan to use apache for the frontal webserver and Seaside/seaside-rest for the request processing.

I work now on a prototype for the test of the solution. Today, i downloaded Pharo 1.1.1 and installed Seaside. I selected WAComancheAdaptor on the port 8080/tcp. That runs perfectly.

In Montichello, I added a repository for seaside30addons and selected seaside-REST-core-pmm and seaside-test-Core. In the "test runner", I have 5 errors :

WAMime TypeStubHandlerTest>>#testMultipleConentTypeRouting
WAMime TypeStubHandlerTest>>#testSimpleAcceptRouting
WAMime TypeStubHandlerTest>>#testSimpleConentTypeRouting
WAPragmaBasedRestfullHandlerTest>>#testCreateRoutes
WAPragmaBaseRouteBuilderTest>>#testPlatformMethods

Must I add another components ?

You need to load Seaside-Pharo-REST-Core as well.

Another little question : seaside-REST allows it to access to the DELETE and PUT commands of HTTP ?

yes.

Norbert

www.auverlot.fr
Olivier,

Take a look at the Seaside-REST code in http://www.squeaksource.com/Seaside30Addons.

With Seaside-REST you can switch cleanly back and forth between stateful and RESTful requests and of course use Seaside facilities for constructing your RESTful responses.

Dale

On 02/11/2011 05:36 AM, Olivier Auverlot wrote:
For a new project, i need to make web services based into the Restful
architecture.My program must read, write, modify and delete informations
in a LDAP directory. I can do that with Perl... but i want to try to use
Pharo and Seaside :)

Someone has experience for this type of application ? How to manage the
HTTP commands (PUT, GET, DELETE and POST) ? Thank you for your help.

Best regards
Olivier

www.auverlot.fr
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside