On Thu, 10 Apr 2003, The Purple Streak, Hilarie Orman wrote:
Thanks for am-id clarification. In general, the OPES processor
won't know how many am's might be sent by the callout server or what
kinds they might be.
If this knowledge is needed, it can be relayed via metadata or
explicitly added to the protocol as an "expect more" flag/parameter.
My expectation is that the possibility of multiple adapted application
messages is application-dependent. Those OPES processors that support
applications like SMTP would wait for the callout server to close the
transaction.
This makes it difficult to know what to start carrying
on the proxied flow.
Not sure what you mean. The number of adapted application messages
does not really affect proxied flow. Usually, OPES processor would
start post-processing and sending out every application message it
receives immediately after it gets app-message-start message (whether
it is the first such message or 10th). Multiple adapted application
messages are only allowed for protocols like SMTP where that is not a
problem, of course. Did I misunderstood your statement?
Should the OPES processor wait until transaction-close?
That seems inefficient.
Why should it? It got an adapted application message it can proceed
with. OCP supports very efficient pipeline where there is no waiting
as long as the application protocol supports such behavior.
See http://www.ietf.org/internet-drafts/draft-ietf-fax-esmtp-conneg-06.txt
for example. There were other SMTP-related examples posted on the
list.
Alex.