Hi Ger,
> >> There is one added complication in that the protocol is a datagram
> >> protocol at a
> >> higher level (although it uses TCP). I am concerned that the whole
> >> protocol could
> >> block if there is not enough data to encrypt a whole
> outgoing message
> >> but the peer cannot
> >> continue until it gets the message.
>
> If you mean that the upper layer protocol is message-oriented rather
> than stream-oriented ('datagram' is a Rorschach blot for me that says:
> UDP sorry) and the protocol is constructed such that outgoing
> message REQ(A) must have produced [a complete] answer message ANS(A)
> before the next outgoing message REQ(B) is sent over the wire, then
> you're in fancy land anyway, as that is not a class 101 scenario for
> TCP, which is by design stream-oriented.
Yes, the higher layers are message oriented. The protocol is not so
restricted as 1:1 request/response though. Several messages can be
sent without any response (dependent on message type). However
only whole messages can be sent and only whole messages can be decoded
by the receiver. Messages must also arrive in the order they were sent.
Thanks for your helpful post.
Regards, Mark.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
