Simple Event Driven Network Library
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros
Public Member Functions | Friends | List of all members
SedNL::EventConsumer Class Reference

A consumer object. It consume certain kind of events from an EventListener. More...

#include <EventConsumer.hpp>

Public Member Functions

 EventConsumer ()
 Construct a consumer.
 EventConsumer (EventListener &producer)
 Construct a consumer consuming events from producer. More...
 ~EventConsumer ()
 Destruct the consumer by calling join.
void set_producer (EventListener &producer) throw (EventException)
 Set the producer. More...
void remove_producer () noexcept
 Remove the previous producer. More...
void run () throw (EventException)
 Start the consumer thread. More...
void join ()
 Join the consumer thread, and stop consuming events.
Slot< Connection & > & on_disconnect ()
 Bind the disconnect event. More...
Slot< TCPServer & > & on_server_disconnect ()
 Bind the server disconnect event. More...
Slot< Connection &, const
Event & > & 
on_event ()
 Bind all unbinded events. More...
Slot< Connection &, const
Event & > & 
bind (std::string event_name)
 Bind a new event. More...


class EventListener

Detailed Description

A consumer object. It consume certain kind of events from an EventListener.

The EventConsumer consume events from an EventListener object. It consume only event that can be processed, i.e. events that have a callback associated (with a call to EventConsumer::bind()).

It runs on it's own thread, using EventConsumer::run(). The thread can be joined with EventConsumer::join().

The main idea is to have one EventConsumer for a bunch of events, and one more for an over bunch, etc.

Two EventConsumer CAN'T consume the same type of events from a common EventListener. If you try to do so, the EventConsumer::run() call will throw an exception, telling that the event are already looked from an other EventConsumer. This is done to force consistency (nothing would prevent two consumer to do different things for the same event).

You can't bind new events while a consumer is running. If you wan't to bind new events, you'll have to join the EventConsumer thread, then add new events, and finaly start it again.

Take a particular care about the behavior of the disconnected event. You CAN'T assume it will be the last event processed, even if you have only one thread. See on_disconnect() documentation.

Here is an example on how EventConsumer allow you to control how much thread you wan't to allow for processing events.

//Some callbacks.
void computation_intensive(Connection&, const Event&);
void loggin(Connection&, const Event&);
void easy_query(Connection&, const Event&);
void lots_of_calls(Connection&, const Event&);
//We assume we have an EventListener named listener.
//Assume we have a computation intensive query.
EventConsumer intensive(listener);
//And an event that is received hundread of times by second
EventConsumer repeated(listener);
//And all remaining events aren't critical
EventConsumer remaining(listener);
//Then, we can launch three threads to consume those events,
//and a the listener thread.;;;;
//And continue our work in the main thread.
//Once we are done, we join all those threads.
//Nb : It's better to always join the listener first.
// If you do so, you are sure that all received
// events are processed.

Definition at line 61 of file EventConsumer.hpp.

Constructor & Destructor Documentation

SedNL::EventConsumer::EventConsumer ( EventListener producer)

Construct a consumer consuming events from producer.

Same effet as calling the empty constructor and then calling set_producer().

[in]producerThe event listener from which events will be consumed.

Member Function Documentation

Slot< Connection &, const Event & > & SedNL::EventConsumer::bind ( std::string  event_name)

Bind a new event.

This function allow binding an event from it's name. Any Event object is constructed with a name, and this name is a string which identify the event. If you bind "foo" with bind("foo").set_function(my_callback), any event with the name "foo" will be dispatched to the callback my_callback.

[in]event_nameName of the event that will be associated with this callback.

Definition at line 43 of file EventConsumer.ipp.

Slot< Connection & > & SedNL::EventConsumer::on_disconnect ( )

Bind the disconnect event.

Callback prototype : void my_on_disconnect(Connection&);

Warning: A disconnect event can be computed before an other event from the same client! This is a consequence of asynchronous nature of a multithreaded environment : nothing prevent the listener to push a new event and a disconnect event while we are processing all disconnect event available. And nothing prevent an other consumer thread to be processing an other event while we start processing a disconnect event. It was experimentaly saw that some time, disconnect event occure before some other events. You are warned! If you wan't to free resources when you receive a disconnected event, you'll have to always check if this resource is available, and remember that it can be destroyed at any time if you have more than one consumer thread.

Definition at line 28 of file EventConsumer.ipp.

Slot< Connection &, const Event & > & SedNL::EventConsumer::on_event ( )

Bind all unbinded events.

This callback will be called for every events that isn't binded by any of the consumers linked to the producer.

You can bind this slot to consume all events not binded by EventConsumer::bind(). You can use use others consumer with the same EventListener producer, but there should be only one providing a on_event() callback. Otherwise, You'll have an 'event collision' when starting the producer (see EventListener::run()).

Definition at line 38 of file EventConsumer.ipp.

Slot< TCPServer & > & SedNL::EventConsumer::on_server_disconnect ( )

Bind the server disconnect event.

Callback prototype : void my_on_server_disconnect(TCPServer&);

This event only happen when the server socket is closed, which is ofted caused by you closing the socket, or network drop.

The same warnings as on_disconnect() apply. You CAN'T assume that this event will be the last event processed from this server. You may see incoming connection after this event was processed.

Definition at line 33 of file EventConsumer.ipp.

void SedNL::EventConsumer::remove_producer ( )

Remove the previous producer.

See set_producer(EventListener&) documentation.

void SedNL::EventConsumer::run ( )
throw (EventException

Start the consumer thread.

Once launcher, the consumer will read events from producer's queues. It will only consume events that are bound by this consumer.

Notice that on_event() allow binding all events not already bound by a consumer (this one or an other one).

void SedNL::EventConsumer::set_producer ( EventListener producer)
throw (EventException

Set the producer.

The producer shoulde live until the EventConsumer die (or, at least, until the EventConsumer stop to use producer, which means that once the producer is destroyed, you shouldn't call run, and the consumer shouldn't be running).

Setting the same producer to two consumer that bind the same event will result in a deffered throw : the call to producer's run will throw an EventException with code EventCollision.

[in]producerThe event listener from which events will be consumed.

The documentation for this class was generated from the following files: