eventstore-0.1.2.0: EventStore Haskell TCP Client

Copyright(C) 2014 Yorick Laupa
License(see the file LICENSE)
MaintainerYorick Laupa <yo.eight@gmail.com>
Stabilityprovisional
Portabilitynon-portable
Safe HaskellNone
LanguageHaskell2010

Database.EventStore

Contents

Description

 

Synopsis

Documentation

data ExpectedVersion Source

Constructors

Any

Says that you should not conflict with anything

NoStream

Stream should not exist when doing your write

EmptyStream

Stream should exist but be empty when doing the write

type Port = Int Source

Result

data Position Source

Constructors

Position 

Instances

data ReadDirection Source

Constructors

Forward 
Backward 

Instances

Event

Connection manager

connect :: Settings -> HostName -> Port -> IO Connection Source

Creates a new connection to a single node. It maintains a full duplex connection to the EventStore. An EventStore Connection operates quite differently than say a SQL connection. Normally when you use a SQL connection you want to keep the connection open for a much longer of time than when you use a SQL connection.

Another difference is that with the EventStore Connection all operation are handled in a full async manner (even if you call the synchronous behaviors). Many threads can use an EvenStore connection at the same time or a single thread can make many asynchronous requests. To get the most performance out of the connection it is generally recommend to use it in this way

Transaction

Re-export