Help save net neutrality! Learn more.
Close

#5 Support for transport interceptors

open
None
4
2007-10-03
2003-05-22
Byrne Reese
No

From Paul, "Support for transport interceptors (custom
headers; access to raw messages (size filters); support
for filters (POP3))."

Perhaps Paul can provide a little more information on
this. Should this be multiple bugs?

Discussion

  • Byrne Reese

    Byrne Reese - 2003-05-22
    • assigned_to: nobody --> paulclinger
    • summary: Support for transport interceptos --> Support for transport interceptors
     
  • Martin Kutter

    Martin Kutter - 2007-10-03
    • labels: 532000 -->
    • milestone: 304765 -->
    • priority: 5 --> 4
     
  • Martin Kutter

    Martin Kutter - 2007-10-03

    Logged In: YES
    user_id=884175
    Originator: NO

    A transport interceptor might be quite useful - for example for spam filtering on POP3 access. However, as POP3 did not become the main SOAP protocol, it's not really important: HTTP messages can be size-limited via LWP::UserAgent, and there's little other use.

    Some interceptor API between transport and decoding (not in the midst of transport) would me much more useful - for example for using encryption/decryption, signing, validation and the like.

    Filed as feature request.

     
  • Martin Kutter

    Martin Kutter - 2007-10-03
    • assigned_to: paulclinger --> kutterma
     

Log in to post a comment.