Thank you very much!
Indy is really a great thing as it does all this.
The only problem is documentation. Though this group seems to solve it.
As for parameters.
The parameters will actually be UTF-8 strings decoded back to WideStrings at
a server. So each parameter on individual line seems to be easier to parse.
More over the number of parameters will be variable (I don't want to pass
default values). And they will be name-bound, not positional. So I've
decided to make the command ASCII only and pass parameters on additional
lines.
It looks like we need an extended version of TIdTCPClient. The current one
lacks functions compared to its server counterpart. For example, an
overloaded version of
SendCmd(Command : string; Parameters: array of string;
Header: TStrings=nil; Body: TStrings=nil)
would be very useful.
As for protocols in general.
Can you give me some link to the docs about RFC-based protocols describing
how to create a new application-level one. All I found in Google are HTTP
references. They describe structure of commands, headers, body, staus codes.
etc. But I need a more general description.
Thanks in advance.
Maxim.
