At Begin, URL Handling and REST

atBegin URL Routing and REST Mapping URLs to Models, Views and Controllers

URL vs. URI • URl is a resource, that asks for action • URL is a ﬁle or a single item that is stateless

URL vs. URI • URl is a resource, that asks for action http://www.lassosoft.com/home/ • URL is a ﬁle or a single item that is stateless

URL vs. URI • URl is a resource, that asks for action http://www.lassosoft.com/home/ • URL is a ﬁle or a single item that is stateless http://www.lassosoft.com/ LassoSoft_Logo.png

URL vs. URI • URl is a resource, that asks for action • URL is a ﬁle or a single item that is stateless

Handling vs. Rewriting vs. Redirecting • Handling is conceptually parsing a URI to see what application components to call to provide a resource. • •

Handling vs. Rewriting vs. Redirecting • Handling is conceptually parsing a URI to see what application components to call to provide a resource. • Rewriting is altering a URL to another one before it even hits the application stack.

Handling vs. Rewriting vs. Redirecting • Handling is conceptually parsing a URI to see what application components to call to provide a resource. • Rewriting is altering a URL to another one before it even hits the application stack. • Redirecting is capturing a request for a URI or URL and sending a different one in lieu.

atBegin • atBegin.lasso placed in Lasso Startup

atBegin.lasso

Apache • Apache conf send ﬁles to Lasso • Done using the Apache site conﬁg, not the .htaccess

Apache Conﬁguration

REST • Really, what it's about is using the true potential of HTTP. • In a RESTful application you'll never modify data using a GET request. • resources being manipulated using a common set of verbs • the actual representation retrieved for a resource is dependent on the request and not the identiﬁer

SOAP RPC • SOAP RPC over HTTP, on the other hand, encourages each application designer to deﬁne a new and arbitrary vocabulary of nouns and verbs • getUsers(), savePurchaseOrder(...)

YUCK • There’s a better way, writing RESTful apps. • Think of each page as a service that responds to requests instead of as a web page.

http verbs in REST • Get • Remember Fielding http://roy.gbiv.com/ • Post Co-founder VP Apache project. • Put • Delete

Developng RESTful URIs • In truly restful apps there are only seven functions.

http verbs in REST • show (Get) • create (Post) • update (Put) • destroy (Delete) • index (Get) • new (Get) • edit (Get)

RESTful URIs • http://www.widgets.co.uk/widgets/edit/2 • http://www.widgets.co.uk/widgets/edit/a76b8fe687c6d1f34d • http://www.widgets.co.uk/customers/create/234 • http://www.widgets.co.uk/customers/list.xml • http://www.widgets.co.uk/clients/destroy/bd76ea87c • http://www.widgets.co.uk/articles/destroy/why-you-should- user-our-widgets_bd76ea87c

How do we handle these? • Routing File or an application controller • /app/controllers/application.inc • map the requests to models, views and controllers

Routing File

Application Structure

At Begin, URL Handling and REST

0 comments

Notes on slide 1

1 Event