Kipsus skrybeletas wrote: > Hi everyone. I can't find a search function anywhere so I'm forced to > ask this. > From a quick review of Synapse, the only client that is capable of > working through a proxy is ThttpSend, and in addition, no SOCKS support > (which severely limits the usability) > If this is so, why is this functionality not integrated in parent class > TSynaClient? I mean, how is checking email a less proxy-worthy activity > than http fetching?
I believe the difference is that HTTP-protocol has the need to accept certain proxy functionality that is based on the specification, whereas email protocols such as SMTP and POP3/IMAP don't... I'll try to clarify the above; in HTTP -protocol, there is a definite specification on how some proxying functions should be implemented on the server side (which is also handled by the same package as the client side functionality in Synapse), but the other protocols don't have such things. I've not played with proxies, but I believe the "proxying" on other protocols happens more on the socket level than on the transport protocol's level. As always, I might be totally of the tangent here... -- Markku Uttula ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
