Jp Calderone wrote:
The iac_FOO method will be called whenever the telnet command FOO is received with the
command's "argument" (the byte following it) as its only argument. When a
subnegotiation is received, iacSBchunk is called.
That's the 1.3 API, anyway. It will still exist in 2.0, but it i
On Mon, 06 Dec 2004 12:52:31 -0600, Donnal Walter <[EMAIL PROTECTED]> wrote:
>I wrote:
> > I've been wanting to get acquainted with Twisted for awhile
> > now, ... BTW, do you know if Twisted's option negotiation
> > uses a callback function? I might download it to take a look, ...
>
> Sorry I did
I wrote:
I've been wanting to get acquainted with Twisted for awhile
now, ... BTW, do you know if Twisted's option negotiation
uses a callback function? I might download it to take a look, ...
Sorry I did not do this earlier, before I posted. It is obvious (now
that I have downloaded it) that Twis
On 2004-12-06, Donnal Walter <[EMAIL PROTECTED]> wrote:
> Grant Edwards wrote:
> > You don't have to start from scratch. The telnet module has
> > hooks built-into it1 so that you can have it call your routines
> > to handle option negotiation. I did it once to impliment some
> > extra Telnet prot
Grant Edwards wrote:
> You don't have to start from scratch. The telnet module has
> hooks built-into it1 so that you can have it call your routines
> to handle option negotiation. I did it once to impliment some
> extra Telnet protocol features, and it wasn't difficult.
Ok, you've inspired me to
Grant Edwards wrote:
> You don't have to start from scratch. The telnet module has
> hooks built-into it1 so that you can have it call your routines
> to handle option negotiation. I did it once to impliment some
> extra Telnet protocol features, and it wasn't difficult.
Ok, you've inspired me to
Grant Edwards wrote:
You don't have to start from scratch. The telnet module has
hooks built-into it1 so that you can have it call your routines
to handle option negotiation. I did it once to impliment some
extra Telnet protocol features, and it wasn't difficult.
Ok, you've inspired me to give it
On Sat, 4 Dec 2004 03:31:12 -0800 (PST), Eyal Lotem <[EMAIL PROTECTED]> wrote:
>
> You simple have to run PyInvoke's server.py on the
> server, and then in the client, you can Pythonically
> control anything on the server:
>
> client = pyinvoke.connect(('some_server', some_port))
> client.modules
I think I have a much simpler solution for you guys..
Assuming you can run arbitrary code on the proprietary
server.
I wrote PyInvoke, and I use it as a much-easier-to-use
replacement for telnet control of computers.
It does require installing Python on the target server
though.
You simple have
Donnal Walter <[EMAIL PROTECTED]> wrote:
>
> Several months ago I tried using the telnet module (on Windows XP) to
> communicate with a proprietary host on our network. This was
> unsuccessful due to problems with "option negotiation", and I gave up on
> the project for a while. I still have n
On Fri, 03 Dec 2004 16:31:40 -0600, Donnal Walter <[EMAIL PROTECTED]> wrote:
>Several months ago I tried using the telnet module (on Windows XP) to
> communicate with a proprietary host on our network. This was
> unsuccessful due to problems with "option negotiation", and I gave up on
> the proj
On 2004-12-03, Donnal Walter <[EMAIL PROTECTED]> wrote:
> Several months ago I tried using the telnet module (on Windows XP) to
> communicate with a proprietary host on our network. This was
> unsuccessful due to problems with "option negotiation", and I gave up on
> the project for a while. I
12 matches
Mail list logo
