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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.