1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96

// MIT License
// 
// Copyright (c) 2019-2021 Alessandro Cresto Miseroglio <alex179ohm@gmail.com>
// Copyright (c) 2019-2021 Tangram Technologies S.R.L. <https://tngrm.io>
// 
// Permission is hereby granted, free of charge, to any person obtaining a copy
// of this software and associated documentation files (the "Software"), to deal
// in the Software without restriction, including without limitation the rights
// to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
// copies of the Software, and to permit persons to whom the Software is
// furnished to do so, subject to the following conditions:
// 
// The above copyright notice and this permission notice shall be included in all
// copies or substantial portions of the Software.
// 
// THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
// IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
// FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
// AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
// LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
// OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
// SOFTWARE.

//! Nsq-client is the [actix](https://actix.rs) based client implementation of the nsq protocol.
//!
//! This crate is intended as a swiss-knife base implementation for more
//! complex nsq client applications, it supports even single or multiple connections, single or
//! multiple async readers.
//!
//! Due the actors model, readers and connections are distinct entities witch communicate
//! each other throught messages, so one reader could receive messages from multiple connections and multiple
//! connections could easily send messages to multiple readers.
//!
//!
//! # Examples
//! ```no-run
//! use actix::prelude::*;
//! use nsq_client::{Connection, Msg, Subscribe, Fin};
//!
//! struct MyReader{
//!     conn: Arc<Addr<Connection>>,
//! };
//!
//! impl Actor for MyReader {
//!     type Context = Context<Self>;
//!     fn started(&mut self, _: &mut Self::Context) {
//!         self.subscribe::<Msg>(ctx, self.conn.clone());
//!     }
//! }
//!
//! impl Handler<Msg> for MyReader {
//!     type Result = ();
//!     fn handle(&mut self, msg: Msg, ctx: &mut Self::Context) {
//!         let conn = msg.conn.clone();
//!         let msg = msg.msg;
//!         info!("MyReader received: {:?}", msg);
//!         conn.do_send(Fin(msg.id));
//!     }
//! }
//! ```

#![feature(try_from, associated_type_defaults)]
extern crate futures;
extern crate tokio_io;
extern crate tokio_codec;
extern crate tokio_tcp;
extern crate bytes;
extern crate hostname;
extern crate serde;
extern crate serde_derive;
extern crate serde_json;
extern crate actix;
extern crate backoff;
extern crate log;
extern crate byteorder;
extern crate fnv;


mod codec;
#[allow(dead_code)]
mod commands;
#[allow(dead_code)]
mod error;
mod config;
mod msgs;
mod producer;
mod conn;
mod subscribe;
mod auth;

pub use subscribe::{Subscribe};
pub use config::Config;
pub use producer::{Producer};
pub use conn::{Connection};
pub use error::Error;
pub use msgs::{Fin, Msg, Reqeue, Touch, Pub, InFlight, OnAuth, OnIdentify, Ready, OnBackoff, OnResume, OnClose, Backoff};