In each request XData provides you with a TXDataOperationContext object with several helper data there, including a thread-safe Manager instance, a connection pool, and the request/response objects: http://www.tmssoftware.biz/business/xdata/doc/web/txdataoperationcontext.htm
Ok - great. Will I also be able to deal with security via this context (eg. disallow to query all entities of a specific type - but only those associated with a specific session id)?
yes, by using custom code. You can send session id in a custom header and check the request for example and process the authorization.
Ok. But I do not understand from the documentation where I can intercept a call into the xdata server.
Well, since you mentioned Sparkle, I thought you were considering using XData service operations, which are more flexible and allow you to implement any server-side code, even non-database related.
Hi. Thanks a lot for your support.
Good. Yes, username/password adds Basic authentication to the server
Hi Wagner - I have a followup on this thread - since the question belongs now to XData I post there in a second.