Web Socket

Web Socket Sécurisé (WSS)


General information has to be set up before it can send requests.
This set up conresponds to a description of the expected elements. This description is called a context.

This part of the documentation appears in the same form as a context.
Refer to the continuation of the documentation to visualize some examples.
It is recommanded to create the contexts from the console, to make things easier.

Context structure

A context is composed of interactions, which are composed of parameters.
An interaction is a request the user can make.
This request can come along with informations needed for its good treatment. The parameters will allow the capture of these informations.
Each parameter can be either "optionnal" and/or "multiple". It enables the definition of the number of elements to research for this parameter.
The parameters are also characterised by their archetype.


This archetype defines the format of the element which is to be found (date, place...). They are of two kinds ;
-Builtins are archetypes already contained in, non-editables. They are made to simplify the capture of complex elements (dates for example.)
-Customs are the archetypes you create yourself.

A customs set is provided by the console, it is called basics.

While creating your archetype custom, there are two things you can define :
- A term list
- Regular expressions
Those elements will allow the capture the the corresponding elements.
The term list will be tolerant to typing and spelling mistakes.


While we are on embedded mode, and we want to run servel by ourselves, it is possible to define an administator password. If defined, this password is required for any modification.

Do you have a question that has not been answered here ?