This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description
Sharrock
========

Sharrock is a Python-based RPC framework design for easy integration into Django. It was created because of my frustrations with the way that many existing REST-based RPC frameworks work. Sharrock is based on the idea that while sometimes it is a good idea to represent RPC as resources (the REST model), other times plain old function calls are what you want.

The central idea of Sharrock is the *descriptor*, a declarative model that both represents the function call at the code level, and additionally provides automatically generated API documentation.

Following the tradition of naming Django projects after Jazz musicians, Sharrock is named after [Sonny Sharrock](http://en.wikipedia.org/wiki/Sonny_Sharrock "Sonny Sharrock Wikipedia page").

Current release is version 0.5.


Basic Parts
-----------
* A *function descriptor* syntax that provides information in both a machine and human readable format about the available functions a service provides, including details of acceptable parameters and return values. The function descriptor also provides the basis for *automated API documentation*.
* A *transport layer* that handles function calls and their return values. Initially Sharrock uses HTTP as a transport layer, but later on I'd like to add a ProtocolBuffer transport.
* *Serialization* of objects in both JSON and XML. In addition serialization of function descriptors as human-readable HTML.
* A *handler* framework for Django, providing hooks to integrate Sharrock into a django app.
* A Python *RPC Client* for Sharrock, making it easy to build client code against a Sharrock service by using the function descriptors.
* An optional *REST* layer that allows functions to be rolled up into resources, and a ResourceClient in Python that allows for RESTful interaction.
* An even more optional ResourceModel layer that binds the Resource functionality to a Django model. See "Model Resources" below for more info.

Requirements
------------

Sharrock requires the following libraries:

* *[Django](http://www.djangoproject.com)* 1.2 or above
* *[requests](http://docs.python-requests.org/en/latest/)* For the client libs.
* *[Markdown](http://www.freewisdom.org/projects/python-markdown/)* for docstring parsing.

Installation
------------

* Use pip to install Sharrock:

pip install -e git://github.com/Saaspire/sharrock.git#egg=Sharrock

* Add "sharrock" to your INSTALLED_APPS.
* In each of your apps that you with to use Sharrock, create a *descriptors.py* module.
* In your root urls, add the following line to your urlpatterns:

(r'^api/',include('sharrock.urls')), # The initial context "api" can be whatever you want.

* Optional: if using the resource layer, mount the resource urls.

(r'^resources/',include('sharrock.resource_urls')),


Descriptors
===========

Remote procedures are created by defining *descriptors*. A descriptor is a declarative model of a remote procedure call (in the way that a Django model is a declarative model of a database table).

from sharrock.descriptors import Descriptor, UnicodeParam

class HelloWorld(Descriptor):
"""
Hello world!
============
"""
name = UnicodeParam('name',default=None,description='The name to address.')

def execute(self,request,data,params):
name = params['name']
if name:
return 'Hello %s!' % name
else:
return 'Hello world!'

A simple function descriptor consists of a subclass of Descriptor. At minimum it must contain a docstring for the class, and an "execute" method. The execute method is called when the function is called remotely.

Descriptor.execute
------------------

The execute method should contain the business logic of the remote procedure. It will be passed 3 significant arguments:

* *request*: The Django request object.
* *data*: A deserialized data object (usually desesrialized from json). If there is a data object, there will be no params.
* *params*: A dictionary of key/value params. If there are params there will be no data object.

Any value the execute method returns should be something that can be serialized back into a response for the client.

Parameters
----------

All parameters can be imported from *sharrock.descriptors*. There are several types of parameters available, each parameter type will attempt to cast incoming values to whatever is its preferred data type. Incoming values that cannot be cast to the data type will raise an exception. Parameter types include:

* UnicodeParam
* IntegerParam
* FloatParam
* BooleanParam
* ListParam
* DictParam
* WildcardParam (any data is good)

Parameters must be instantiated with the first argument being the name of the parameter, and then with the following optional keyword arguments:

* *required*: If True, this parameter is required. False by default. If a call is made on the function and a required parameter is missing, a ParamRequired exception will be raised.
* *default*: The default value for the parameter, if it is not specified. Only makes sense for non-required parameters.
* *description*: The description of the parameter, to be used in the automatically generated documentation.

Data Parsing
------------

For descriptors meant to post serialized data (JSON, XML etc) instead of keyword arguments, set the `data_parsing` flag to `True` for the descriptor. This will alert Sharrock to apply the parameters to the deserialized data, and not keyward arguments. Obviously if you have required parameters for a descriptor set to data parsing and you post query parameters to it, it will fail with a ParamRequired exception.

Descriptor Docstrings
---------------------

The documentation system will automatically create documentation based on the descriptor docstring. It will read documentation in Markdown format and format it appropriately from that.

Deprecating Descriptors
-----------------------

You can deprecate descriptors by settings a deprecation message at the individual descriptor, at the resource or at the module level. Setting the deprecation message looks like this:

deprecated = 'You should stop using this function.'

The descriptor will be shown as deprecated in the API docs. Additionally, when it is called, the server will append a **Warning** response header to the response with a message indicating that the function is deprecated.

Deprecation is inherited, so if a module is marked as depreated then all resources and descriptors within that module will be deprecated. Likewise if a resource is marked deprecated then all of its member descriptors will be deprecated.

API Versions
============

The version of your API can simply be defined by setting the following variable in your descriptors.py file:

version = "1.0"

If you do not define the version for your API, Sharrock will automatically define it as "0.1dev".

Maintaining Multiple Versions of an API
---------------------------------------

Sometimes it makes sense to maintain multiple versions of the same app's API. In this case, make descriptors a package (a folder with an __init__.py file). Within the package, create individual modules (files) for each version of the API you want to maintain. In each version module, make sure you define the *"version"* variable.

In the package's __init__.py file, make sure you include each version module in the __all__ variable.

Executing Functions
===================

Functions may be executed with the following url pattern:

(api mount point)/(app)/(version)/(function slug)

So for example, if you had an app called "MyApp", the version "1.0" and the function "MyFunction", and the mountpoint for Sharrock was "/api/" then the call would be:

/api/myapp/1.0/myfunction/

Functions don't inheirantly expect any particular http method, although if they are expecting a data upload they'll only be able to get that through POST and PUT methods.

API Documentation
=================

API documentation can be found at the "/dir/" context. For example:

/api/dir/

Specific app and version documentation can be found by appending the app and version to the context:

/api/dir/myapp/1.0/

Specific descriptors can be retrieved through the 'describe' context, in various formats (with HTML as default). For example:

/api/describe/myapp/1.0/myfunction/

or

/api/describe/myapp/1.0/myfunction.json
/api/describe/myapp/1.0/myfunction.xml

The API docs will show the full path to the function or resource call. You can set the root of the URL with the `SHARROCK_API_ROOT` and `SHARROCK_RESOURCE_ROOT` settings, respectively. This should match up to your domain URL and the mount point you used in your views. So for example:

SHARROCK_API_ROOT = 'https://www.example.com/api'
SHARROCK_RESOURCE_ROOT = 'https://www.example.com/api/resource'

If no roots are set, the API docs will display ellipsis ("...") in place of the roots.

HttpClient
==========

*sharrock.client.HttpClient* is a simple RPC client class designed to consume Sharrock function descriptors and execute remote Sharrock procedure calls. It is inspired by the Python XML-RPC client.

The HttpClient will locally cache descriptors and, by default, perform local param checking on function calls. It uses JSON serialization to communicate with the server.

HttpClient.__init__
-------------------

* *service_url*: The full URL to the server, including the API mount context. For example "http://example.com/api".
* *app*: The app to address, for example "myapp".
* *version*: The version of the API to use, for example "1.0".
* *auth_user=USERNAME*: Optional. Will pass the username to basic auth.
* *auth_password=PASSWORD*: Optional. Will pass the password to basic auth.

To use the HttpClient, simply execute method calls on it, with the slugified name of the function as the method name. All methods take the optional keyword argument "data" for data objects to be serialized and uploaded, and treat other keyword arguments as params.

For example, taking the "HelloWorld" descriptor from above:

from sharrock.client import HttpClient

c = HttpClient('http://example.com/api','myapp','1.0')
c.helloworld(name='Loren')

A Note About Basic Auth and the HttpClient
------------------------------------------

The HttpClient (and ResourceClient) will accept the keyword args `auth_user` and `auth_password` which they'll use in Basic Auth: concatenating them together, base64 encoding them and appending them to an `Authorization: Basic` header.

When working with the Axilent platform, the API token is used as the `auth_user`, with no password being set.

The same client example as above, but using basic auth:

from sharrock.client import HttpClient

c = HttpClient('http://example.com/api','myapp','1.0',auth_user='Loren',auth_password='MYSEKRIT')
c.helloworld(name='Fred')

Creating RESTful Services
=========================

In Sharrock, REST is implemented as an optional layer on top of the basic function layer. This is based on the concept that while sometimes functionality is appropriately modeled as resources, sometimes its better to represent it as plain old procedure calls.

Resources are also defined in your descriptors.py file. Resources simply reference Descriptor objects and assign them to appropriate HTTP methods.

from sharrock.descriptors import Descriptor, Resource

class GetHello(Descriptor):
"""
Gets a big hello.
"""
def execute(self,request,data,params):
return 'Why hello!'

class Greeting(Resource):
"""
A resource for a greeting.
"""
get = GetHello()

In the above example, the GetHello function has been assigned to the "get" method of the Greeting resource. Resources may assign Descriptors to "get", "post", "put" and "delete" attributes.

Hiding Descriptors
------------------

When using Descriptors as resource methods, often its desirable to prevent the descriptors from being individually accessible as functions in the API. This can be done by setting their "visible" attribute as False.

class MyGetter(Descriptor):
"""
Gets stuff.
"""
visible = False

def execute(self,request,data,params):
pass

class MyResource(Resource):
get = MyGetter()

Now the MyGetter function will be available via the MyResource resource, but not as an individual function.

Executing Resources
-------------------

Resources are executed via the following URL pattern:

(resource mount point)/(app)/(version)/(resource slug)

for example:

/resources/myapp/1.0/myresource

Sharrock will route the request to the appropriate descriptor, based on the http method of the request. If the incoming request uses a method that has not been defined in the resource the Sharrock will return a 403 (Method Not Allowed) error code.

Resource Client
---------------
Sharrock supplies *sharrock.client.ResourceClient*, an HTTP client for REST-style operations. An instance of a ResourceClient represents a single resource, with the various HTTP method operations available for it.

* `ResourceClient.__init__(service_url,app,version,resource_slug,auth_user='',auth_password='')`: Instantiates the client towards a single resource.

* `ResourceClient.get(data=None,params=None,local_params_check=True)`
* `ResourceClient.post(data=None,params=None,local_params_check=True)`
* `ResourceClient.put(data=None,params=None,local_params_check=True)`
* `ResourceClient.delete(data=None,params=None,local_params_check=True)`

The HTTP methods all have the same signature: Either a JSON object may be posted as data, or key/value params (but not both) and a flag that indicates params should be checked on the client (setting it to False supresses this function). If the resource descriptor does not define a method, the corresponding attribute will be None instead of a method. All of the HTTP methods will return a deserialized response from the server.

Exactly like the HttpClient, the ResourceClient will append an `Authorization: Basic` header to requests if the `auth_user` or `auth_password` keyword args are set.

Model Resources
===============
A common case is to use the REST layer to directly manipulate Django models. While many REST frameworks assume this is the center case, I have purposefully packaged it as an add-on to the core REST functionality, which is itself an add-on to the basic RPC functionality. One could accomplish the same thing with a Resource implementation, so just think of this as a shortcut.

Model Resources are easy to define:

from sharrock.modelresource import ModelResource
from myapp.models import MyModel

class MyModelResource(ModelResource):
"""Resource for my model."""
model = MyModel

That's about it. Your model resources are defined in the same descriptors.py file where you would put any other descriptors or ressource definitions. Model resources are mounted under the resource URL mount-point, the same as other resources.

Model Resource Client
---------------------
Sharrock provides a special client for model resources, sharrock.client.ModelResourceClient, to provide convenience methods for model CRUD operations. Usage is very similar to the ResourceClient.

* ModelResourceClient.__init__(service_url,app,version,resource_slug)

* ModelResourceClient.list(): Lists all of the models
* ModelResourceClient.get(model_pk): Retrieves the model with the specified key.
* ModelResourceClient.create(**attrs): Creates a new model with the specified attributes.
* ModelResourceClient.update(model_pk,**attrs): Updates an existing model.
* ModelResourceClient.delete(model_pk): Deletes the specified model resource client.

Note: Added Table of Contents capabilities.

Converting ObjectDoesNotExist exceptions to HTTP 404 Responses
==============================================================

For APIs in which a specific object is addressed by some lookup parameter, the entire operation should fail if the object can't be located. Sharrock provides a shorthand to convert ObjectDoesNotExist exceptions into a 404 response to be sent back to the API client, by means of the `not_found_as_404` decorator.

To use, simply decorate the descriptor's `execute` method:

class MyDescriptor:
...
@not_found_as_404
def execute(self,request,data,params):
# any code that raises ObjectDoesNotExist will trigger a 404 response

Release History

Release History

0.7.4.1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.7.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.7.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.8

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.7

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.5

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.4

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.3

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.2.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.2.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.2

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6.1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.6

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
Sharrock-0.7.4.1.tar.gz (21.9 kB) Copy SHA256 Checksum SHA256 Source Sep 7, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting