Raja,
Good clarifications.
Actually you can use the CPA to setup the type of route-not-read
handling you describe - because internally we're doing this at NIH -
where we have ebMS deployed in two places - so the CPA is used
thus:
(External party) CPA' - ebMS (NIH Msg gateway) - CPA'' -
ebMS (NIH app server) - CPA''' - NIH App
Each CPA is tailored for the role and msg handling required.
Admittedly the specification is somewhat quiet on this usage - perhaps
this is something we could spell out in a FAQ or use notes...
The chunking handling is similar to stage delivery - except that
once the stream of chunks is started - the push continues until
its done. Persumably the first chunk contains information about how
many more chunks will follow?
Thanks, DW
"The way to be is to do" - Confucius (551-472
B.C.)