Øyvind Harboe wrote:
> You can call that a defined over the wire protocol if you want to.
>
> But this is all further down the line.
Then - later we hash out the wire line protocol.
I have always been talking about the narrow subject of "the wireline
protocol".
I'm ok with that.
-Duane.
___
On Sat, Jul 12, 2008 at 2:06 PM, Duane Ellis <[EMAIL PROTECTED]> wrote:
> There is always an "over the wire protocol" you can dance around the issue
> all you want.
I intend to modify the tcl server to let the *client* decide what to
do with a connection, the data coming in and what data to send b
There is always an "over the wire protocol" you can dance around the issue all
you want.
As you say:
>> The client *decides* what code to run on the server(e.g. on
>> the OpenOCD command line + injects scriptlets, etc.)
Thus the defined over the wire protocol is:
(A) the invoking of e
It just occurred to me:
Even if we allow TCP/IP connections to talk to the OpenOCD, that doesn't
make the format on the wire the API.
A HTTP server is a server where the client is under no circumstances allowed
to execute code on the server.
With OpenOCD this is not the case. The client *decides
