1 file was added to this release more than 14 days after its initial publication. Inspect the release files before installing.
========
`djazator`_ is a simple django plugin for sending push messages from
django server to sockjs clients. It internally uses `zeromq`_ and
`sockjs-tornado`_. djazator can send push notifications to all sockjs
clients and to subset of this clients.
Requirements:
-------------
1. `pyzmq`_>=2.0
2. `sockjs-tornado`_>=0.0.5
3. `django`_>=1.4
Installation:
-------------
Install ``djazator`` with your favorite Python package manager:
::
pip install djazator
Add ``djazator`` to your ``INSTALLED_APPS`` in ``settings.py``
::
INSTALLED_APPS = (
'django.contrib.auth',
'djazator',
...
)
Define ``DJAZATOR_MQ_SOCKET`` in ``settings.py``
::
DJAZATOR_MQ_SOCKET = 'tcp://127.0.0.1:8002'
Usage:
------
Run zeromq forwarder device
::
djazator-mq --sub=tcp://127.0.0.1:8002 --pub=tcp://127.0.0.1:8001
Run sockjs-tornado server
::
djazator-server --port=8080 --mq_socket=tcp://127.0.0.1:8001 --route=/sockjs --address=''
Alternatively, if you don't need multiple tornado instances support, you can entirely omit djazator-mq and should pass -S/--single argument to djazator-server
::
djazator-server --single --port=8080 --mq_socket=tcp://127.0.0.1:8002 --route=/sockjs --address=''
Append sockjs client library to your page
::
<head>
<script src="http://cdn.sockjs.org/sockjs-0.3.min.js">
...
Open page in browser and connect to sockjs-tornado server
::
conn = new SockJS('http://localhost:8080/sockjs')
Define a callback for incoming messages
::
conn.onmessage = function (e){ console.log(e.data); };
Send a message from django
::
from djazator.pub import notify_all
notify_all({'msg': u'Hi all!'})
and you will see it in js console
::
Object {msg: "Hi all!"}
Advanced notifications:
-----------------------
You can send notifications to subset of users.
::
from djazator.pub import notify
from djazator.utils import tokenize
from django.contrib.auth.models import User
user = User.objects.get(email='djazator@mail.com')
notify({'msg': u'Hi, %s!' % user.username}, users=[user])
token = tokenize(user)
notify({'msg': u'Hi user with token %s !' % token}, users=[user])
To get this messages you need to subscribe by token
::
var token = {% djazator_token %};
SockJS.prototype.emit = function (name, data) { // wrapper around SockJS.send for djazator's protocol support
var meta_dict = {
name:name,
data:data
};
this.send(JSON.stringify(meta_dict))
};
conn = new SockJS('http://localhost:8080/sockjs')
conn.emit('subscribe', {'token': token});
conn.onmessage = function (e){ console.log(e.data); };
``{% djazator_token %}`` is nothing more than a wrapper around
``djazator.utils.tokenize`` that returns user.id signed with
standart django singing mechanism. You can configure you own salt by setting
``DJAZATOR_SALT`` in ``settings.py``. If you need more security,
you can provide your own tokenization function. It should accept django User
object and return token. Add path to this function in settings.py .
::
DJAZATOR_TOKENIZER = 'path.to.my.func'
Conclusions:
------------
1. djazator serializes datetime objects with ISO 8601 format. You can parse it on client with `moment.js`_ .
2. djazator server can handle client's messages constructed only in some specific way and can't be used for client to client communications.
Production:
-----------
1. `Hipache`_
.. _djazator: https://github.com/mike-grayhat/djazator
.. _zeromq: http://www.zeromq.org/
.. _moment.js: http://momentjs.com/
.. _sockjs-tornado: https://github.com/mrjoes/sockjs-tornado
.. _pyzmq: https://github.com/zeromq/pyzmq
.. _django: https://www.djangoproject.com/
.. _Hipache: https://github.com/dotcloud/hipache
Metadata
Release files for djazator 0.2.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
File added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| djazator-0.2.5.tar.gz | 6.5 kB | Without provenance | Details for djazator-0.2.5.tar.gz |
Release files / djazator-0.2.5.tar.gz
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | djazator-0.2.5.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa0a65c27eca2807d30edcfd90093ca9a43e324037bc457b068b8447a6274f42
|
|
BLAKE2b-256 checksum How to use checksums |
b3ca8206912ff672df6b1e52ff6c39e45a39cf6be73d0355cfd5fafcc1f90640
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for djazator 0.2.5
Upload timing
Release file added late
1 file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.