There is one common scenario with virus filtering in a callout server
that I wrote about some time ago.
Do you think an additional message type could help and is worth here?
Scenario:
A virus filter often cannot send chunks of data back to the OPES
processor before it has the complete data. Only then it can start
the scanning process.
On the other hand it modifies data only in rare situations.
Most results are "no virus found, use original message unmodified".
Only if virus was found, it modifies (repair) the data or replaces
it in parts or completly by an error message.
So a possible message from callout server to OPES processor could be
<data-not-yet xid amid change-probability progress>
It informs the OEPS processor that the callout server is working on
this although it does not reply data now. If "change-probability" is
low, the OPES processor could use techniques to fight the raising
latency time,
for example:
- some kind of download progress indication,
- "data trickling" or
- the proposed LateClearance content encoding
(see draft-stecher-lclr-encoding-00.txt)
The "progress" parameter can inform that the callout processor needs
even more time although all data was already received (e.g. an archive
needs to be extracted first which is a currently ongoing lengthy
process)
Thanks
Martin