Hi,
Please see my comments inline.
Thanks,
Raymond
----- Original Message -----
From: "Simon Laws" <[EMAIL PROTECTED]>
To: "tuscany-dev" <[email protected]>
Sent: Thursday, July 19, 2007 3:31 PM
Subject: Relating ServiceReference/CallableReference to the reference proxy?
CallableReference presents an interface for setting and getting
conversation
information.
I think CallableReference is not only for conversation. It's more like an
endpoint reference which contains the address (uri and properties) and state
(parameter).
When it comes time to dispatch a message the information is
required in the invoker handler. There is not direct relationship between
these two structures. The current mechanism of using the
ThreadMessageContext to transfer bits of this information is suspect in my
opinion because the conversation information in question is related to the
message to be sent and not to the context of the message that was
received.
I think we should move into more message-oriented than invocation-oriented.
The Message should carry more metadata (message headers). When the message
reaches an implemention/binding provider, the provider will create context
out of the message and present them to the impl/binding (on the thread, or
in binding-specific way).
I could bend the (non spi) interfaces to pass the originating service
reference into the WireObjectFactor, ProxyService and hence on into the
proxy/invoker handler. Looks a bit tricky due to the way it's structured
atm.
Without changing interfaces I could invent a hidden method on the proxy to
accept a reference to the ServiceReference which can be used to get
conversation information as required.
Is there an obvious (easy) way that these are/can be associated?
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
