The old (1.2.beta23) patch is tagged as scrapped because it isn't done
in the proper way, and because of this it isn't maintained either. It is
available as a reference more than a patch.
I am on the way to construct a new implementation acheiving the same
goal in request processing flow and structure, but done in a quite
different way. It is made from scratch with the lessions learnt from the
earlier attemt and discussions with other Squid developers. The sad news
is that I have found myself to have very little time to spend on Squid
development lately (all Squid things I do is on my spare time, not part
of my work).
I hope to be able to present something withing the next weeks. Much of
the basic structure is in place, but I have not yet dared to try to
fully compile the beast, or even less run it. There are some things left
to implement, and then probably quite a bit of debugging and collection
of loose ends before there is something usable.
The current request processing code is flawed in more than one way, and
I have never liked how it is done (well, it was fine before the
introduction of persistent connections, but not afterwards)
Regards
Henrik Nordstr�m
Spare time Squid hacker
Bassem Bohsali wrote:
>
> Hi Mr. Nordstrom
> I was following the discussion made on Squid's ability to redirect the
> Propfind method, which happened last May. I applied the first patch and the
> result was as mentioned in the conversation. So, when I tried to apply the
> second patch- called "New way of processing request bodies (PUT/POST)" it
> didn't apply properly to squid 2.2.STABLE3 (well, it was meant for
> 1.2.beta23 and was
> tagged as scrapped) and resulted in compilation errors.
> Is there a way to achieve this objective or did I/you get to a dead end
> (for the moment at least)?
>
> Best Regards,
> ~~~~~~~~~~~~~
> Bassem Bohsali
> Network Engineer
> Transmog s.a.l
> ~~~~~~~~~~~~~
Received on Wed Jun 16 1999 - 17:12:07 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:46:54 MST