Marak

@line-o - As for waiting for linux support...if you can find a place that will give you a mac os x server, we could simply call to that over HTTP?...

In order to make the datastore work for other languages will require a slight refactor. Instead of requiring that the service use a redis client, the service instead should only...

@pyhedgehog - I did a bit more research. I think implementing IPC via child_process.send() could be the best option. see: https://nodejs.org/api/child_process.html#child_process_options_stdio This would require that the python `run-hook-python` binary would...

I've currently got IPC working locally over stdio `3` and `4`. The issue I have now is actually implementing a callback API over stdio message passing interface...err... For example, if...

So I've opted for moving all datastore logic into an HTTP client library. For node services, this will be a seamless API transition ( all javascript datastore services will remain...

@pyhedgehog Additional languages can now talk to the datastore inside any hook service. In order to enable this for python, we'll need a python version of [hook.io-sdk](https://github.com/bigcompany/hook.io-sdk) built. It should...

@pyhedgehog ping. if we port hook.io-sdk to a python version then datastore ( and all other API methods ) would work from python.

Most excellent! Thank you so much. :-)

@kauegimenes - Yes. We have a web admin and HTTP Rest endpoint for datastore....it's checked into the repo, but not deployed yet. In final testing. Hopefully will release it soon.

@kauegimenes - We don't have an all endpoint available, but we do have recent: http://hook.io/datastore/recent I don't think there is a specific reason why we couldn't implement `Datastore.all`.