Results 1 to 3 of 3

Thread: Dispatch Intercepts in Python

  1. #1
    Netmaster0000's Avatar
    Netmaster0000 is offline Registered User
    Name: Neel Edwards
    Organization: Home(Student)
    Project: Server based application wide security.
    Join Date
    Dec 2008
    Posts
    21

    Question Dispatch Intercepts in Python

    I was reading up on the dispatch intercept on chapter 28 and there's no explanation for how it is done in python. I began to attempt to even translate the C++ code shown into python, but there's no Ice.DispatchInterceptor type. All I'm trying to do is intercept a call before it is dispatched to the respective server call so that i can query information about where the call is coming from. Pretty similar to examining soap headers for the User Agent and Remote Address. In this case my ultimate goal is to be able to recognize the client of the user - such as whether it's a C++, .NET, Java or Python client, and see the ip address that the request is coming from. This will significantly help in regards of associating this information with a logged in user/session.

  2. #2
    bernard's Avatar
    bernard is offline ZeroC Staff
    Name: Bernard Normier
    Organization: ZeroC, Inc.
    Project: Ice
    Join Date
    Feb 2003
    Location
    Palm Beach Gardens, FL
    Posts
    1,294
    Hi Neel,

    Dispatch interceptors are currently available in C++, Java, C# and Objective-C, but not in Python.

    Maybe you could use a servant locator as a work-around.

    Best regards,
    Bernard
    Bernard Normier
    ZeroC, Inc.

  3. #3
    Netmaster0000's Avatar
    Netmaster0000 is offline Registered User
    Name: Neel Edwards
    Organization: Home(Student)
    Project: Server based application wide security.
    Join Date
    Dec 2008
    Posts
    21

    Thumbs up

    Thanks. The servant locator may not even be neccessary since i can get the information from the "current" parameter which to each operation on the server side. I get sufficient information from current.con.toString(). I'll work with that. Thanks for the suggestion of servant locators however, I think it'll even help to differentiate servant locators based on categories and designate one per each type of "user agent" so to speak. So since the applications will vary per implementation language, the servant locators should vary for each by the category. This will definitely do.
    "Nothing is gained without sacrificing something of equal value..." Principles of Life: Equivalent Trade

    ŪNetŪ

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Asynchronous Dispatch Interceptor
    By trivian in forum Help Center
    Replies: 4
    Last Post: 06-27-2008, 02:12 PM
  2. Dynamic dispatch demo
    By orphean in forum Help Center
    Replies: 3
    Last Post: 12-21-2005, 02:06 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •