The 'do you wanna let this connection happen' dialog - problem is already
solved:
-----Mensaje original-----
De: tripack44 [mailto:no_reply@...]
Enviado el: miercoles, 03 de julio de 2002 5:08
Para: twsapi@...
Asunto: twsapi: Re: automated login
--- In twsapi@y..., Carl Erikson <carlerikson@y...> wrote:
A hack is to send keystrokes to the login window.
Pass your username as separate keystrokes. Then send
a tab key. Then send your password as separate
keystrokes. Then send a return. There is a setting
to pre-fill the username in the .ini file (sorry, no
pre-fill for the password):
[Logon]
Username=edemo
Are you sure there is no pre-fill in? I just tried it with password
field added such as the following example (:
[Logon]
Username=pfloyd5
Password=darkside
and it worked.
This is the jts.ini file in the \jts directory.
-----Ursprungliche Nachricht-----
Von: grozzie2 [mailto:grozzie2@...]
Gesendet: Saturday, July 27, 2002 10:33 PM
An: twsapi@...
Betreff: Re: twsapi: Java Events-- avoinding the API
I've heard some folks have decompiled the TWS and modified the code
themselves -- long before the API became available.
The reason I kind of like an api into TWS, it bypasses all the
hassles of logins etc. A raw socket api on the server end, is going
to introduce a security layer.
With that said, there are a couple of things I'd like to see in TWS
itself, to accomodate fully external driven environments. First off,
would be great if it didn't pop up that 'do you wanna let this
connection happen' dialog, and it would be even better, if we could
run it in a 'dont even draw any windows' mode, to allow it to be run
on a totally headless system, that has no monitor, no keyboard, and
no video subsystems even loaded, aka a remote *nix setup.
