Skip to main content
This is a pre-production deployment of Warehouse. Changes made here affect the production instance of PyPI (
Help us improve Python packaging - Donate today!

Client library for scirocco proyect.

Project Description
# Scirocco Pyclient
[![Build Status](](

This is a handy library to interact with the [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](

## Installation

This client library has two main install methods.

#### From source:
git clone
python3 install

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

## Using the client

#### The response object

Every operation in this client will return the same [response object](sciroccoclient/
, 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]( 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.


from sciroccoclient.httpclient import HTTPClient

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

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

from sciroccoclient.messages import SciroccoMessage

# Preparing our fixed message properties.

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

# Pushing an object

msg.payload = {"type": "message"}

#Pushing a string message payload

msg.payload = 'message'

# Pushing binary payload

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

# 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)

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

#### 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.


response_object = scirocco.pull()

# print message metadata

# print the message 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.

#### 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 ( in its pull operation to confirm
the message by id. For example if we want to confirm '5823a70203c123003de4229b'
message id , the code will be :


#### 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.


#### 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.


# Limiting results by 10 (ordered by creation date)


#### Updating a message

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

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.


#### 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.


## Running tests
For running tests you will need and instance of [scirocco-server]( project up and running.

git clone
cd scirocco-pyclient
python3 test
Release History

Release History

History Node


This version
History Node


History Node


History Node


History Node


Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
scirocco-pyclient-v2.0.2.linux-x86_64.tar.gz (17.7 kB) Copy SHA256 Checksum SHA256 any Dumb Binary Nov 19, 2016
scirocco-pyclient-v2.0.2.tar.gz (10.4 kB) Copy SHA256 Checksum SHA256 Source Nov 19, 2016

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