Dan Pascu wrote:
so, the syntax part is managed by the transport modules and can be
different from transport to transport.
as yo said, for FIFO it is not an issue as it a stream like connection
- you read until the other party closes the connection.
it's not an issue for STREAM like connectins that close after the command,
but it is if they don't.
as it is about OpenSER to client part, openser will always close the
communication after sending the reply. otherwise it will be a bug :)
we will consider this aspects when we will develop new module,
especially the one oriented on DATAGRAM communication.
I think this is important to do for STREAM connections as well. What if I
don't want to close the stream connection after a request, but want to
keep it open and issue multiple commands on it?
well...this is an open subject - if a stream connection should be reused
for future commands or closed after the first one. but we have them both
(as a matter of configuration) - also the commands may include such
information (if the client wants to keep the connection up or not).
Besides it won't hurt to have 2 LF at the end of the message, no matter
what kind of transport they use, it'll only make the messaging clearer
and more consistent across all MI implementations.
it will not hurt I guess, but this will apply only to the text oriented
transports (not for xmlrpc or http).
regards,
bogdan
_______________________________________________
Devel mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/devel
