> Suggestion: instead of separate functions for plain and encrypted
> messages, we should probably let the class keep track of whether
> encryption has been set up, and act accordingly. Trying to send
> plaintext after a session key has been established won't work, nor
> will encrypted traffic without a key.
My C API does this. It has two main functions for data transmittal:
OpenSRS_read and OpenSRS_write, which know whether or not encryption is
necessary. OpenSRS's perl API behaves in the same fashion.
> Lookups are also handled *completely* differently than other commands:
> different server and port, and different message format. We'll need
> to take that into account.
Indeed. My C API has a separate function for lookups. It stores the
connection information separately and leaves the data connection open (until
explicit close, shutdown, or timeout) so that lookups are speedy.
.---------------------------------------------------------------.
| bleachboy bboy at bboy dot net +1 (615) 260-4931 |
| ICQ 1839892 UNIX: Because you want to USE your computer |
`---------------------------------------------------------------'
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:22 EDT