|Re: [ecf-dev] Sending crendentials with every request|
On 21.03.2020 05:33, Scott Lewis wrote:
Not completely sure I understand what you are wanting to do, but you could look at overriding these methods:Sometime it's not that easy to describe the use-case, but in fact your suggestions were helpful and pointed me in the right direction.
If you want to add to what's sent in every rpc, you could add to the 1 (what client sends) and to 2 (what server received and how processes it) by adding your meta-data to the Request instance that's sent (has to be Serializable of course).That helped. I'm thinking about replacing
with my own class which extends SharedObjectMsg and adds the additional meta-data.
Currently I'm looking for the right place to register my own RegistrySharedObject implementation on client side (on server side i already have that).
On client side i already have a IConsumerContainerSelector with an overriden createContainer method, but haven't found a good point to intercept the object creation of RegistrySharedObject. There is a lot of Adapter and Factory stuff going on ;)
Maybe you can suggest a good solution.
Back to the top