Alexis' log

Introducing cornice

2011-12-06T00:00:00+01:00

Wow, this is my second working day at mozilla. I've been working, yesterday and -today, on a pyramid REST-ish toolkit, cornice.

Cornice allows you to take out from you all the repetitive stuff you do when -writing a web service. I'm mainly thinking about different kinds of validation.

+Alexis' loghttp://blog.notmyidea.org2011-12-06T00:00:00+01:00Introducing cornice2011-12-06T00:00:00+01:00Alexis Métaireautag:blog.notmyidea.org,2011-12-06:/introducing-cornice.html/

Wow, already my third working day at mozilla. Since Monday, I've been working with +Tarek Ziadé, on a pyramid REST-ish toolkit named cornice.

Its goal is to take all the hard bits appart from you when implementing a web +service, so you can focus on what's important. Cornice provides you facilities +for validation of any kind.

The goal is to simplify your work, but we don't want to reinvent the wheel, so +it is easily pluggable with validations frameworks, such as Collander.

Handling errors and validation

We have changed the way errors are handled. Here is how it works:

service = Service(name="service", path="/service")
+
+
+def is_awesome(request):
+    if not 'awesome' in request.GET:
+        request.errors.add('body', 'awesome', 'You lack awesomeness!')
+
+
+@service.get(validator=(is_awesome))
+def get1(request):
+    return {"test": "succeeded"}
+

All the errors collected during the validation process, or after, are collected +before returning the request. If any, a error 400 is fired up, with the list of +problems encoutred encoded as a nice json list (we plan to support multiple +formats in the future)

As you might have seen, request.errors.add takes three parameters: location, +name and description.

location is where the error arised. It can either be "body", "query", "headers" +or "path". name is the name of the variable causing problem, if any, and +description contains a more detailled message.

Here is an example of a malformed request:

+$ # run a demo app
+

To describe a web service in cornice, you have to write something like this

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 14)

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 54)

Content block expected for the "code-block" directive; none found.

 .. code-block:: python
 
-

How are you handling your shared expenses?

2011-10-15T00:00:00+02:00

TL;DR: We're kick-starting a new application to manage your shared expenses. Have a look at http://ihatemoney.notmyidea.org

As a student, I lived in a lot of different locations, and the majority of them diff --git a/feeds/all.atom.xml b/feeds/all.atom.xml index 25b595b..2e4fdc1 100644 --- a/feeds/all.atom.xml +++ b/feeds/all.atom.xml @@ -1,18 +1,49 @@ -Alexis' loghttp://blog.notmyidea.org2011-12-06T00:00:00+01:00Introducing cornice2011-12-06T00:00:00+01:00Alexis Métaireautag:blog.notmyidea.org,2011-12-06:/introducing-cornice.html/

Wow, this is my second working day at mozilla. I've been working, yesterday and -today, on a pyramid REST-ish toolkit, cornice.

Cornice allows you to take out from you all the repetitive stuff you do when -writing a web service. I'm mainly thinking about different kinds of validation.

+Alexis' loghttp://blog.notmyidea.org2011-12-06T00:00:00+01:00Introducing cornice2011-12-06T00:00:00+01:00Alexis Métaireautag:blog.notmyidea.org,2011-12-06:/introducing-cornice.html/

Wow, already my third working day at mozilla. Since Monday, I've been working with +Tarek Ziadé, on a pyramid REST-ish toolkit named cornice.

Its goal is to take all the hard bits appart from you when implementing a web +service, so you can focus on what's important. Cornice provides you facilities +for validation of any kind.

The goal is to simplify your work, but we don't want to reinvent the wheel, so +it is easily pluggable with validations frameworks, such as Collander.

Handling errors and validation

We have changed the way errors are handled. Here is how it works:

service = Service(name="service", path="/service")
+
+
+def is_awesome(request):
+    if not 'awesome' in request.GET:
+        request.errors.add('body', 'awesome', 'You lack awesomeness!')
+
+
+@service.get(validator=(is_awesome))
+def get1(request):
+    return {"test": "succeeded"}
+

As you might have seen, request.errors.add takes three parameters: location, +name and description.

Here is an example of a malformed request:

+$ # run a demo app
+

To describe a web service in cornice, you have to write something like this

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 14)

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 54)

Content block expected for the "code-block" directive; none found.

 .. code-block:: python
 
-

Quels usages pour l'informatique ?

2011-12-01T00:00:00+01:00

Quand on termine ses études, on s'en pose un tas, des questions. Sur le métier que l'on veut faire, sur ce que ça signifie, sur le sens et la valeur du travail. Et j'en suis arrivé à faire un constat simple: l'informatique, c'est diff --git a/feeds/mozilla.atom.xml b/feeds/mozilla.atom.xml index 6a63bb5..9669fc0 100644 --- a/feeds/mozilla.atom.xml +++ b/feeds/mozilla.atom.xml @@ -1,16 +1,47 @@ -Alexis' loghttp://blog.notmyidea.org2011-12-06T00:00:00+01:00Introducing cornice2011-12-06T00:00:00+01:00Alexis Métaireautag:blog.notmyidea.org,2011-12-06:/introducing-cornice.html/

Wow, this is my second working day at mozilla. I've been working, yesterday and -today, on a pyramid REST-ish toolkit, cornice.

Cornice allows you to take out from you all the repetitive stuff you do when -writing a web service. I'm mainly thinking about different kinds of validation.

+Alexis' loghttp://blog.notmyidea.org2011-12-06T00:00:00+01:00Introducing cornice2011-12-06T00:00:00+01:00Alexis Métaireautag:blog.notmyidea.org,2011-12-06:/introducing-cornice.html/

Wow, already my third working day at mozilla. Since Monday, I've been working with +Tarek Ziadé, on a pyramid REST-ish toolkit named cornice.

Its goal is to take all the hard bits appart from you when implementing a web +service, so you can focus on what's important. Cornice provides you facilities +for validation of any kind.

The goal is to simplify your work, but we don't want to reinvent the wheel, so +it is easily pluggable with validations frameworks, such as Collander.

Handling errors and validation

We have changed the way errors are handled. Here is how it works:

service = Service(name="service", path="/service")
+
+
+def is_awesome(request):
+    if not 'awesome' in request.GET:
+        request.errors.add('body', 'awesome', 'You lack awesomeness!')
+
+
+@service.get(validator=(is_awesome))
+def get1(request):
+    return {"test": "succeeded"}
+

As you might have seen, request.errors.add takes three parameters: location, +name and description.

Here is an example of a malformed request:

+$ # run a demo app
+

To describe a web service in cornice, you have to write something like this

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 14)

System Message: ERROR/3 (./content/mozilla/introducing-cornice.rst, line 54)

Content block expected for the "code-block" directive; none found.

 .. code-block:: python
 
-