The Ecore Con events can be categorized into Server side events and Client side events. Server side events:

ECORE_CON_CLIENT_ADD: Whenever a client connection is made to an Ecore_Con_Server, an event of this type is emitted, allowing the retrieval of the client's ip with ecore_con_client_ip_get and associating data with the client using ecore_con_client_data_set.
ECORE_CON_EVENT_CLIENT_DEL: Whenever a client connection to an Ecore_Con_Server is destroyed, an event of this type is emitted. The contents of the data with this event are variable, but if the client object in the data is non-null, it must be freed with ecore_con_client_del.
ECORE_CON_EVENT_CLIENT_DATA: Whenever a server object receives data, then an event of this type is emitted. The data will contain the size and contents of the message sent by the client. It should be noted that data within this object is transient, so it must be duplicated in order to be retained. This event will continue to occur until the client has stopped sending its message, so a good option for storing this data is an Eina_Strbuf. Once the message has been received in full, the client object must be freed with ecore_con_client_free.

Client side events:

ECORE_CON_EVENT_SERVER_ADD: Whenever a server object is created with ecore_con_server_connect, an event of this type is emitted, allowing for data to be serialized and sent to the server using ecore_con_server_send. At this point, the http handshake has occurred.
ECORE_CON_EVENT_SERVER_DEL: Whenever a server object is destroyed, usually by the server connection being refused or dropped, an event of this type is emitted. The contents of the data with this event are variable, but if the server object in the data is non-null, it must be freed with ecore_con_server_del.
ECORE_CON_EVENT_SERVER_DATA: Whenever client object receives data from the server, an event of this type is emitted. The data will contain both the size and contents of the message sent by the server. It should be noted that data within this object is transient, so it must be duplicated in order to be retained. This event will continue to occur until the server has stopped sending its message, so a good option for storing this data is an Eina_Strbuf. Once the message has been received in full, the server object must be freed with ecore_con_server_free.

Typedefs
typedef struct _Ecore_Con_Event_Client_Add	Ecore_Con_Event_Client_Add
typedef struct _Ecore_Con_Event_Client_Upgrade	Ecore_Con_Event_Client_Upgrade
typedef struct _Ecore_Con_Event_Client_Del	Ecore_Con_Event_Client_Del
typedef struct _Ecore_Con_Event_Client_Error	Ecore_Con_Event_Client_Error
typedef struct _Ecore_Con_Event_Server_Add	Ecore_Con_Event_Server_Add
typedef struct _Ecore_Con_Event_Server_Upgrade	Ecore_Con_Event_Server_Upgrade
typedef struct _Ecore_Con_Event_Server_Del	Ecore_Con_Event_Server_Del
typedef struct _Ecore_Con_Event_Server_Error	Ecore_Con_Event_Server_Error
typedef struct _Ecore_Con_Event_Client_Data	Ecore_Con_Event_Client_Data
typedef struct _Ecore_Con_Event_Server_Data	Ecore_Con_Event_Server_Data
typedef struct _Ecore_Con_Event_Client_Write	Ecore_Con_Event_Client_Write
typedef struct _Ecore_Con_Event_Server_Write	Ecore_Con_Event_Server_Write
typedef struct _Ecore_Con_Event_Proxy_Bind	Ecore_Con_Event_Proxy_Bind