[
Lists Home |
Date Index |
Thread Index
]
Hi Roger,
Roger L. Costello wrote:
>Ah, you want to know my use case? I've been deliberately vague on this
>as it is a bit sensitive but I'll give the essense.
>
>
>
Ah yes, telemetry logging. That's good, I know nothing about telemetry.
But that's not going to stop me from suggesting a totally different
approach. May I suggest that you consider using a web service. Use WSDL
to define a reverse implementation, in other words your "clients" (in
the business sense) will be implemented as servers for this web service.
Then send the data for each logging event as a single client call,
perhaps using a state attribute [*] to maintain the context that would
otherwise be implied as the SAX document.
Most platforms now have the capability to generate basic clients and
servers from a WSDL spec., so your clients should be reasonably content,
and as discussions here have noted, you will be sending the data
straight through the front door into their web server, which will - in
my experience - simplify security negotiations considerably.
Francis.
[*] or you could use the web service transaction support proposed in the
Sun / BEA or IBM / Microsoft / BEA proposals which were all published
last week but seem not to have been mentioned in this forum.
--
"Never mind manoeuvre, go straight at 'em." - Admiral Horatio Nelson
|
