//! Synchronous Session API
//!
//! The synchronous session API is the most convenient way to use this driver.
//! It is provided by the `rincon_session` crate.
//!
//! Here is some example code to showcase the basic usage of the session API:
//!
//! ```rust,dont_run
//! # extern crate rincon_core;
//! # extern crate rincon_connector;
//! # extern crate rincon_session;
//! # #[macro_use] extern crate serde_derive;
//! # extern crate tokio_core;
//! # use rincon_core::api::connector::Connector;
//! # use rincon_core::api::datasource::DataSource;
//! # use rincon_connector::http::JsonHttpConnector;
//! # use rincon_session::{ArangoSession, Result};
//! # use rincon_session::client::Document;
//! # use tokio_core::reactor::Core;
//! # use std::str::FromStr;
//! #
//! # fn main() {
//! #    let datasource = DataSource::from_str("http://localhost:8529")
//! #        .expect("invalid URL for datasource")
//! #        .with_basic_authentication("root", "s3cur3");
//! #
//! #    let mut core = Core::new().unwrap();
//! #
//! #    let connector = JsonHttpConnector::new(datasource, &core.handle()).unwrap();
//! #
//! #    let session = ArangoSession::new(connector, core);
//! #
//! #    fn create_doc<C>(session: ArangoSession<C>) -> Result<()>
//! #        where C: 'static + Connector
//! #    {
//! #
//! #[derive(Debug, Clone, PartialEq, Serialize, Deserialize)]
//! struct Person {
//!     name: String,
//!     age: u16,
//! }
//!
//! let person = Person { name: "herbert".to_string(), age: 42 };
//!
//! let friendsbook = session.use_database_with_name("friendsbook");
//! let people = friendsbook.create_collection("people")?;
//!
//! let doc_header = people.insert_document(person)?;
//!
//! let (_, doc_key, _) = doc_header.deconstruct();
//! let document: Document<Person> = people.get_document(doc_key)?;
//! #
//! #        Ok(())
//! #     }
//! # }
//! ```
//!
//! If you have a closer look at this example you may ask what this `session` is
//! that we are accessing in the second `let` statement. This is an
//! `ArangoSession` instance from the `rincon_session` API. Lets create such
//! an `ArangoSession` instance step by step.
//!
//! To use the `rincon_session` API add this to your `Cargo.toml`:
//!
//! ```toml
//! [dependencies]
//! rincon_core = "0.1"
//! rincon_session = "0.1"
//! rincon_connector = "0.1"
//! tokio-core = "0.1"
//! ```
//!
//! And in your crate root add this:
//!
//! ```rust
//! extern crate rincon_core;
//! extern crate rincon_connector;
//! extern crate rincon_session;
//! extern crate tokio_core;
//! ```
//!
//! The `tokio_core` crate is needed for instantiating a `Connector` as we will
//! see in a moment.
//!
//! First we configure a `DataSource` for our [ArangoDB] server. A `DataSource`
//! is a struct that holds the parameters needed to connect to a concrete
//! installation of [ArangoDB].
//!
//! ```rust
//! # extern crate rincon_core;
//! use rincon_core::api::datasource::DataSource;
//! use std::str::FromStr;
//!
//! fn main() {
//!     let datasource = DataSource::from_str("http://localhost:8529")
//!         .expect("invalid URL for datasource")
//!         .with_basic_authentication("root", "s3cur3");
//! }
//! ```
//!
//! Next we create a `Connector` which will be used to communicate with the
//! [ArangoDB] server. The `Connector` defines which transport protocol is used
//! and how the payload is serialized. We choose the provided
//! `JsonHttpConnector` which support HTTP and HTTPS and serializes the payload
//! as JSON.
//!
//! ```rust
//! # extern crate rincon_core;
//! # extern crate rincon_connector;
//! # extern crate tokio_core;
//! use rincon_core::api::datasource::DataSource;
//! use rincon_connector::http::JsonHttpConnector;
//! use tokio_core::reactor::Core;
//! use std::str::FromStr;
//!
//! fn main() {
//!     let datasource = DataSource::from_str("http://localhost:8529")
//!         .expect("invalid URL for datasource")
//!         .with_basic_authentication("root", "s3cur3");
//!
//!     let mut core = Core::new().unwrap();
//!
//!     let connector = JsonHttpConnector::new(datasource, &core.handle()).unwrap();
//! }
//! ```
//!
//! The `new()` method of the `JsonHttpConnector` takes 2 arguments. The first
//! argument is the datasource we have just created before. The second argument
//! is a handle to `reactor::Core` from the `tokio_core` crate.
//!
//! And finally we create an `ArangoSession`:
//!
//! ```rust
//! # extern crate rincon_core;
//! # extern crate rincon_connector;
//! # extern crate rincon_session;
//! # extern crate tokio_core;
//! use rincon_core::api::datasource::DataSource;
//! use rincon_connector::http::JsonHttpConnector;
//! use rincon_session::ArangoSession;
//! use tokio_core::reactor::Core;
//! use std::str::FromStr;
//!
//! fn main() {
//!     let datasource = DataSource::from_str("http://localhost:8529")
//!         .expect("invalid URL for datasource")
//!         .with_basic_authentication("root", "s3cur3");
//!
//!     let mut core = Core::new().unwrap();
//!
//!     let connector = JsonHttpConnector::new(datasource, &core.handle()).unwrap();
//!
//!     let session = ArangoSession::new(connector, core);
//! }
//! ```
//!
//! Now we are ready to conveniently interact with the [ArangoDB] server as
//! shown in the example at the beginning of this chapter.
//!
//! [ArangoDB]: https://www.arangodb.com

#![doc(html_root_url = "https://docs.rs/rincon_session/0.1.0")]

#![warn(
    missing_copy_implementations,
    missing_debug_implementations,
    missing_docs,
    trivial_casts,
    trivial_numeric_casts,
    unsafe_code,
    unstable_features,
    unused_import_braces,
    unused_qualifications,
)]

extern crate futures;
extern crate serde;
extern crate tokio_core;

extern crate rincon_core;
extern crate rincon_client;

mod arango_session;
mod collection_session;
mod cursor_session;
mod database_session;
mod edge_collection_session;
mod graph_session;
mod vertex_collection_session;

pub use self::arango_session::*;
pub use self::collection_session::*;
pub use self::cursor_session::*;
pub use self::database_session::*;
pub use self::edge_collection_session::*;
pub use self::graph_session::*;
pub use self::vertex_collection_session::*;

pub mod client {
    //! Re-export of types from the `rincon_client` crate that are used in the
    //! public API of this crate.

    pub use rincon_client::admin::types::{ServerVersion, TargetVersion};
    pub use rincon_client::aql::types::{ExplainedQuery, ExplainOptions, ParsedQuery};
    pub use rincon_client::collection::types::{Collection, CollectionProperties,
        CollectionPropertiesUpdate, CollectionRevision, CollectionStatus,
        CollectionType, NewCollection, RenameTo};
    pub use rincon_client::cursor::types::{Cursor, CursorStatistics, NewCursor,
        Warning};
    pub use rincon_client::database::types::{Database, NewDatabase};
    pub use rincon_client::document::types::{Document, DocumentHeader, DocumentId,
        DocumentKey, DocumentModifyOptions, DocumentReplaceOptions, DocumentUpdate,
        NewDocument, UpdatedDocument, UpdatedDocumentHeader};
    pub use rincon_client::graph::types::{EdgeCollection, EdgeDefinition, Graph, NewEdge, NewGraph,
        VertexCollection};
    pub use rincon_client::user::types::{NewUser, Permission, User, UserExtra,
        UserUpdate};
}

use rincon_core::api::connector::Error;

/// The `Result` type returned by methods of this crate.
pub type Result<T> = ::std::result::Result<T, Error>;