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
# Scirocco Pyclient
[![Build Status](https://travis-ci.org/eloylp/scirocco-pyclient.svg?branch=master)](https://travis-ci.org/eloylp/scirocco-pyclient)


This is a handy library to interact with the [scirocco-server](https://github.com/eloylp/scirocco-server) project. If you dont know about it , please read first that project docs.

Please if you want contribute to this project read [this](CONTRIBUTING.md)

## Installation

This client library has two main install methods.

#### From source:
```bash
git clone https://github.com/eloylp/scirocco-pyclient.git
python3 setup.py install
```

#### From pip3:
```bash
pip3 install scirocco-pyclient
```

## Using the client

#### The response object

Every operation in this client will return the same [response object](sciroccoclient/responses.py)
, representing the state of the operation as well as the resultant message payload representation.

#### Instantiating the client

You must instantiate the HTTPClient by passing three params.
Respectively they are:

* [scirocco-server](https://github.com/eloylp/scirocco-server) endpoint (take care about http/https schema).
* Your pre-stablished by convention node id (hexadecimal string, will be a mongo Objectid in future).
* The master auth token for gain access to that scirocco-server instance.

```python

from sciroccoclient.httpclient import HTTPClient

scirocco = HTTPClient('http://localhost', 'af123', 'DEFAULT_TOKEN')
```

#### Pushing messages
Pushing messages is simple as populate [scirocco message object](sciroccoclient/messages.py).

```python
from sciroccoclient.messages import SciroccoMessage

# Preparing our fixed message properties.

msg = SciroccoMessage()
msg.node_destination = 'af123'

# Pushing an object

msg.payload = {"type": "message"}
scirocco.push(msg)

#Pushing a string message payload

msg.payload = 'message'
scirocco.push(msg)

# Pushing binary payload

with open('file.bin', 'rb') as f:
msg.payload = f.read()
msg.payload_type = '.bin'
scirocco.push(msg)

# Pushing scheduled messages, 4 days in future (All in UTC).
from datetime import datetime, timedelta

msg.payload = 'This is an scheduled message.'
msg.scheduled_time = datetime.utcnow() + timedelta(days=4)
scirocco.push(msg)

```
Some tips about above code are:

* payload_type property is a 50 characters free field for determining
how data must be handled in the consumer part. If not setted scirocco will
populate it with detected mime type.
* Scheduled messages, are messages that are not available to consumers
until reaching scheduled_time in time frame. **Warning** , this is not
the "consuming time", only the moment that are marked as "available" to
consumers.

#### Receiving messages

You will receive messages in the same data type as you send it, except for binary
type. You will push binary , and the item is stored as binary , but you will receive
it in base64 representation.

```python

response_object = scirocco.pull()

# print message metadata
print(response_object.metadata.__dict__)

# print the message payload.
print(response_object.payload)
```

If no pending messages the client will return None else, it will return
a response object which contains metadata and payload. The message
will change its status to 'processing', so it cannot be accesible by other
'pull' operation.

##### The on_receive callback

If you want to make a process that listens for incoming messages, you only need
to generate a callback function that encapsulates all the logic that must
process each message and create a consumer.

Callback function requirements are:

* Must have two positional arguments
* First for receiving the client it self for further operations,
like ack current message.
* Second argument will be the message received, in the form of [SciroccoMessage](sciroccoclient/messages.py#L6) Object .

```python

def callback(client, message):
print(message.payload)
client.ack(message.metadata.id)

scirocco.on_receive(callback)
```

Above example blocks the process and waits for messages, that its contents
will be throw into stdout.

If you do not want this behaviour and want this to be asynchronous you can specify
at second parameter and let the program continue its execution. This will return the Thread
object, (https://docs.python.org/3.6/library/threading.html#thread-objects)
for let you control thread execution.

```python

on_receive_thread = scirocco.on_receive(callback, True)
print("Im ready, send me a message.")

# shutting down the consumer - thread
on_receive_thread.shutdown()

```

By default, the pull interval is set to 0.5 seconds. **its important**
tune it according your needs. Remember that , at this time this is not
a real time solution so dont abuse so much the server !

```python

scirocco.on_receive(callback, False, 2) # last param its the pull interval, in this case augmented to 2 seconds.

```

If you want exiting the program from inside the callback function, you need to use
the SciroccoInterruptOnReceiveCallbackError exception.This will shutdown the thread in your custom circunstances.

```python

def callback(client, message):

# do your stuff here

if message.payload['shutdown']:
client.ack(message.metadata.id)
raise SciroccoInterruptOnReceiveCallbackError

scirocco.on_receive(callback)
```


#### Confirming messages (ack operation)

When you deal with IPC (inter process communications) or interdependant operations in different processes,
you need to mark the message as "processed" for further operations
in other processes.

You only need to save the id of the message that will be confirmed from
response object (response_object.metadata.id) in its pull operation to confirm
the message by id. For example if we want to confirm '5823a70203c123003de4229b'
message id , the code will be :

```python
scirocco.ack('5823a70203c123003de4229b')
```


#### Reviewing a message

If you only need to watch the status of a message/es ,
call for get function, passing as parameter the id of message. Like this.

```python
scirocco.get('5823a70203c123003de4229b')
```


#### Getting all messages incoming/sended to/by this node

You optionally can pass a first argument to limit the returned results.
Anyway, it will be limited by a server side config parameter.

```python
scirocco.get_all()

# Limiting results by 10 (ordered by creation date)
scirocco.get_all(10)

```

#### Updating a message

As first parameter the id of the message. As second parameter the new data
payload.

```python
scirocco.update_one(msg_id, new_payload)
```

#### Deleting a message

You must specify as first parameter id of the message to be permanent removed
from the system no matters its state. Cannot be undone.

```python
scirocco.delete_one('5823a70203c123003de4229b')
```

#### Deleting all messages

Delete from the system all messages incoming/sended to/by this node.
This operation only may be executed if you want a total reset of the node and
its actions. Cannot be undone.

```python
scirocco.delete_all()
```

## Running tests
For running all tests you will need and instance of [scirocco-server](https://github.com/eloylp/scirocco-server) project up and running at localhost.

```bash
git clone https://github.com/eloylp/scirocco-pyclient.git
cd scirocco-pyclient
python3 setup.py test
```
Release History

Release History

v2.1.3

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

v2.0.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

v2.0.0

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

v1.0.0

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

v0.0.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

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
scirocco-pyclient-v2.1.3.linux-x86_64.tar.gz (21.8 kB) Copy SHA256 Checksum SHA256 any Dumb Binary Nov 22, 2016
scirocco-pyclient-v2.1.3.tar.gz (12.8 kB) Copy SHA256 Checksum SHA256 Source Nov 22, 2016

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development 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