Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Sending crendentials with every request
  • From: Peter Hermsdorf <peter.hermsdorf@xxxxxxxxx>
  • Date: Mon, 23 Mar 2020 16:30:53 +0100
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nr34zvN+H8ejEa6zPq2Uk6c2VMR1JzGtx6QgU7rtEA4=; b=gisExXGDgOk2wTtRiR8X7LJ00LmqkN2qlhZpoontc7T4Ml1lPiUbdpIOXgRrSWReFkOyasWEVl2mN9Ekxy4JHooyUxDH1mxguvkzYlHU6VhrZA+Sk3AeSJhnqoVZeaCCv4LFb1O1JxCEg54zt6upcglcUWAzC9hr6LI2JRQJ1JoSZrE6SuleI72+vT+53Uy/NNf0a6T6H/433YbTjGsp0TQenaqyX7NrUzzyrFRyfKKtFxOMYW71kUowPt3VFHVtADO5Lm2aOFHSpikTei82vmdwwBb5MFDORTCIrWOzaqS1h8052P8hdlHiypRRTbxzwXhk8AI0mP9aLW/hWq6GyA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=Q0WnhEJhW9tjRVoMeiB8nOqrZgblS/SoDxQ7NXEEE4j/CAO/6Jo7dNKmQpJvh4p43mxoGEPtIuV0SYkKmixINlvIHUSM6CikJ6rkBPYWEo6P4osBP4ZBe1PT8Ea/+N2WFz4mTPvP4n/ed2Yalp9NOa01MePEJLpwR8QMwqQLL+K4++CneieFhNYsrxusZE5rkjwTt26961uafwp4HdhoRccfum1FlhtqU1scjddrUmwB8j30G+ShAZuGs4fZAqRlwwUpHtG/CrdTyp3nmwqDhpyjTBEX0Wcn7e+lByBOq99hP7K6cMnpdkot7rePapF8BXus9xH704fP3NHw7vJH6g==
  • Delivered-to: ecf-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

Hi Scott,

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).

Does that help?
That helped. I'm thinking about replacing

SharedObjectMsg.createMsg(CALL_REQUEST, request)

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