Pranav Desai wrote:
Hello All,
What would you suggest should be the way to include SCTP support in Squid 3.0 ?
As Henrik said it sound like you are on the right track However I would
make two suggestions.
It's slightly too late for 3.0, take a look at the 3.1 code instead.
In order to make Squid select some SCTP and some TCP you may also need
to look into an ACL control for people to setup their own decision
logics of when to try each. With a failover, as a first guestimate I'd
think SCTP when asked, with old TCP as a backup if it fails.
My assumption here is that SCTP would be useful for clients (which
support SCTP) connecting using slow/lossy wireless type networks. My
goal is to experiment and compare the performance against TCP for
wireless networks.
So, I started with that and was easily able to add a config option for
client-side and change the corresponding function
clientHttpConnectionsOpen() to set appropriate protocol type and it
worked just fine. But that would make it an SCTP only proxy.
We could also open up another listening port for SCTP, so that we can
have both SCTP and TCP simultaneously, where the origin server side
will always be TCP.
But I feel that I am missing something here. So, I would really
appreciate any suggestions or comments you may have.
Thanks for your time.
-- Pranav
--
Please use Squid 2.7.STABLE1 or 3.0.STABLE6
