Archived
This forum has been archived. Please start a new discussion on GitHub.
Contexts
Hello,
I have a little question about the differences of context between
CORBA and Ice.
Without discussing if it's better to have a clean signature of operations,
that causes the need of interceptors, or explicit extra arg to pass
context from client to server, I would like to know what is the
approach to follow to pass objects in the context (i.e., TransactionService).
Should I stringify the identity ?
Maybe it would be nice to have the possibility of putting arbitrary
data.
Thanks in advance,
Guido.
I have a little question about the differences of context between
CORBA and Ice.
Without discussing if it's better to have a clean signature of operations,
that causes the need of interceptors, or explicit extra arg to pass
context from client to server, I would like to know what is the
approach to follow to pass objects in the context (i.e., TransactionService).
Should I stringify the identity ?
Maybe it would be nice to have the possibility of putting arbitrary
data.
Thanks in advance,
Guido.
0
Comments
-
A context in Ice is more comparable with CORBA service contexts (in the GIOP protocol), not with the evil IDL context :-)
A context is for passing information *about* a request, such as routing information. For example, Glacier uses contexts to control batching, security, etc. Have a look at the Glacier manual for more details.
Contexts should never be used as regular parameters. They might be interpreted and changed or even dropped by routers.
Contexts will also be the mechanism with which distributed transactions will eventually be implemented in Ice.0
