Thank you again!
As for extended version of TCPClient.
I agree now. It looks like I wanted a whole RPC here. And if so it would
result in SOAP ;-)
But since my task is much simpler I will not try to invent a bike here.
Maxim.
>
> > It looks like we need an extended version of TIdTCPClient.
>
> No, you do not.
>
> > The current one lacks functions compared to its server counterpart.
>
> As it should be, because TIdTCPClient is not a server component. However,
> Indy 10 does have a TIdCmdTCPClient component, which has the exact same
> CommandHandler support that TIdCmdTCPServer has.
>
> > For example, an overloaded version of
> >
> > SendCmd(Command : string; Parameters: array of string;
> > Header: TStrings=nil; Body: TStrings=nil)
> >
> > would be very useful.
>
> No, it wouldn't. For starters, it would complicate TIdTCPClient itself.
> And second, it has no use in any other Indy component at all, so there is
no
> reason to put it into Indy directly. What you ask for is custom behavior,
> and as such you should be wrapping that kind of functionality in your own
> function that formats the necessary values for the existing SendCmd() to
> use.
>
> > Can you give me some link to the docs about RFC-based protocols
>
> Every protocol is described in its own separate RFC. The documentation
> lists which component implements which RFCs.
>
> > describing how to create a new application-level one.
>
> There are no docs for that.
>
> > All I found in Google are HTTP references. They describe structure of
> > commands, headers, body, staus codes. etc.
>
> That is what RFCs do to begin with.
>
> > But I need a more general description.
>
> Such as?
>
>
> Gambit
