Subject | RE: [IB-Java] Digest Number 10 |
---|---|
Author | J.T. Wenting |
Post date | 2000-08-09T10:00:22Z |
As an option, yes. As the default, it would probably lead to too much
overhead for applications that do not need it like servlets/intranet
applications (encrypting/decrypting are usually expensive operations).
Jeroen T. Wenting
jwenting@...
Murphy was wrong, things that can't go wrong will anyway
overhead for applications that do not need it like servlets/intranet
applications (encrypting/decrypting are usually expensive operations).
Jeroen T. Wenting
jwenting@...
Murphy was wrong, things that can't go wrong will anyway
> -----Original Message-----<commercials snipped>
> From: Peter Harrison [mailto:peterha@...]
> Sent: Wednesday, August 09, 2000 11:31
> To: IB-Java@egroups.com
> Subject: Re: [IB-Java] Digest Number 10
>
>
> One feature that would be nice in InterClient is Encryption. This way it
> could be used across the internet to connect to databases.
> Native Interbase
> isn't ideal because of the number of pings back and forth it does over the
> wire. Interclient is better because there is a request and a response (as
> far as I can tell), making it idea for the Internet.
>
> Does anyone else think this would be a nice addition to InterClient?
>