Metadata-Version: 1.0
Name: durian
Version: 0.0.2
Summary: Webhooks for Django **EXPERIMENTAL**
Home-page: http://github.com/ask/durian/
Author: Ask Solem
Author-email: askh@opera.com
License: UNKNOWN
Description: ============================================================================
        durian - Web Hooks for Django
        ============================================================================
        
        :Version: 0.0.1
        
        .. image:: http://cloud.github.com/downloads/ask/durian/webhooks-logo.png
        
        Introduction
        ============
        
        We want the web sites we create to communicate with other sites. To enable
        this we give the clients an URL they can connect to. This is fine for most
        requests, but let's take a look at RSS.
        
        RSS publishes your articles for others to subscribe to. Whenever you have a
        new article to publish you add it to the RSS document available at an URL
        like::
        
        http://example.com/articles.rss
        
        The client connects to this URL, say, every 20 minutes to check if there's
        something new. And if there is something new, it has to re-download the entire
        content, even if it already has some of the articles from before.
        We call this communication method `pulling`_.
        
        This is where web hooks (or HTTP callbacks) comes in, instead of giving the
        clients an URL they can connect to, the clients *give you an URL* you connect
        to every time there is something to update.
        
        By `pushing`_ instead of pulling the updates, both you
        and your clients saves bandwidth, sometimes by a lot.
        
        .. image:: http://cloud.github.com/downloads/ask/durian/webhook-callback2.png
        
        You can read more about web hooks at the `Web Hooks Blog`_.
        These slides by Jeff Lindsay is a good introduction to the subject:
        `Using Web Hooks`_.
        
        .. _`Web Hooks Blog`: http://blog.webhooks.org
        .. _`Using Web Hooks`:
        http://www.slideshare.net/progrium/using-web-hooks
        .. _`pushing`: http://en.wikipedia.org/wiki/Push_technology
        .. _`pulling`: http://en.wikipedia.org/wiki/Pull_technology
        
        **NOTE** This software is just in the planning stage and is going to
        change drastically. You can follow what is happening here, and is welcome to
        help out making it happen, but you should probably not use it for anything
        until it has reached an alpha version.
        
        
        Creating an event
        -----------------
        
        In this example we'll be creating a ModelHook.
        
        A ModelHook is a hook which takes a Django model and signal.
        So whenever that signal is fired, the hook is also triggered.
        
        You can specify which of the model fields you want to pass on to the listeners
        via the ``provides_args`` attribute.
        
        
        First let's create a simple model of a person storing the persons
        name, address and a secret field we don't want to pass on to listeners:
        
        >>> from django.db import models
        >>> from django.utils.translation import ugettext_lazy as _
        
        >>> class Person(models.Model):
        ...     name = models.CharField(_(u"name"), blank=False, max_length=200)
        ...     address = models.CharField(_(u"address"), max_length=200)
        ...     secret = models.CharField(_(u"secret"), max_length=200)
        
        
        Now to the hook itself. We subclass the ModelHook class and register it in
        the global webhook registry. For now we'll set ``async`` to False, this means
        the tasks won't be sent to ``celeryd`` but executed locally instead. In
        production you would certainly want the dispatch to be asynchronous.
        
        >>> from durian.hook import ModelHook
        >>> from durian.registry import hooks
        >>> from django.db.models import signals
        
        
        >>> class PersonHook(ModelHook):
        ...     name = "person"
        ...     model = Person
        ...     signal = signals.post_save
        ...     provides_args = ["name", "address"]
        ...     async = False
        >>> hooks.register(PersonHook)
        
        Now we can create ourselves some listeners. They can be created manually
        or by using the web-interface. A listener must have a URL, which is the
        destination callback the signal is sent to, and you can optionally filter
        events so you only get the events you care about.
        
        >>> # send event when person with name Joe is changed/added.
        >>> PersonHook().listener(
        ...     url="http://where.joe/is/listening").match(
        ...     name="Joe").save()
        
        >>> # send event whenever a person with a name that starts with the
        >>> # letter "J" is changed/added:
        >>> from durian.match import Startswith
        >>> PersonHook().listener(
        ...     url="http://where.joe/is/listening").match(
        ...     name=Startswith("J").save()
        
        >>> # send event when any Person is changed/added.
        >>> PersonHook().listener(url="http://where.joe/is/listening").save()
        
        The filters can use special matching classes, these are:
        
        * Any()
        Matches anything. Even if the field is not sent at all.
        
        * Is(pattern)
        Strict equality. The values must match precisely.
        
        * Startswith(pattern)
        Matches if the string starts with the given pattern.
        
        * Endswith(pattern)
        Matches if the string ends with the given pattern
        
        * Contains(pattern)
        Matches if the string contains the given pattern.
        
        * Like(regex)
        Match by a regular expression.
        
        
        In this screenshot you can see the view for selecting the person event:
        
        .. image::
        http://cloud.github.com/downloads/ask/durian/durian-shot-select_event.png
        
        and then creating a listener for that event:
        
        .. image::
        http://cloud.github.com/downloads/ask/durian/durian-shot-create_listenerv2.png
        
        
        View for listening URL
        ----------------------
        
        >>> from django.http import HttpResponse
        >>> from anyjson import deserialize
        
        >>> def listens(request):
        ...     payload = deserialize(request.raw_post_data)
        ...     print(payload["name"])
        ...     return HttpResponse("thanks!")
        
        
        Installation
        ============
        
        You can install ``durian`` either via the Python Package Index (PyPI)
        or from source.
        
        To install using ``pip``,::
        
        $ pip install durian
        
        
        To install using ``easy_install``,::
        
        $ easy_install durian
        
        
        If you have downloaded a source tarball you can install it
        by doing the following,::
        
        $ python setup.py build
        # python setup.py install # as root
        
        Examples
        ========
        
        .. Please write some examples using your package here.
        
        
        License
        =======
        
        BSD License
        
        
        Contact
        =======
        
        Ask Solem <askh@opera.com>
        
Platform: any
Classifier: Development Status :: 1 - Planning
Classifier: Framework :: Django
Classifier: Environment :: Web Environment
Classifier: Topic :: Internet :: WWW/HTTP
Classifier: Topic :: Communications
Classifier: Intended Audience :: Developers
Classifier: Programming Language :: Python
Classifier: Operating System :: OS Independent
Classifier: License :: OSI Approved :: BSD License
