====== Daemon Protocol ======
'>>' : Message sent by client

'<<' : message sent by server
<code>
>> HELO\t$versione\t$token\r\n
<< 250\t$welcomeMessage OR 401\t$notAuthorizedMessage\r\n
>> LIST SERVICE\r\n
<< $codeName\n$codename\n.....\r\n
>> USE $codeName\r\n
<< 250\t$serviceChangedMessage\r\n (SQL Like)
>> LIST COMMANDS\r\n (or >> LIST COMMANDS\t$codeName\r\n)
<< $cmdName[\t$parameters]\n$cmdName[\t$pa...\r\n
>> EXEC\t$cmdName[\t$parameters]\r\n (or >> EXEC:$codeName\t$cmdName....)
<< 250\t$result\r\n OR 401\t$notAuthorized\r\n OR 404\t$cmdNameNotFound OR 500\t$error\r\n
>> BYE
<< BYE 

</code>

Questions:
- is this meant for a totally new protocol/totally new daemon: e.g. all commands and parameters what to do are given in the protocol, so the daemon does not need to look up infos in the database?
- maybe another approach would be: keep the daemon more or less as is but completely separate the "productive data" from the "edit data" - and maybe increase the possibilities with the "status" field (maybe somthing like a command field).

Discussions...?? :-)