Re: future of icap-patch
Hi, Ok the news for icap-patch for squid are not good. I am putting some effort and I believe that day by day will become more stable. Baumgaertel Oliver wrote: I've taken a look at 2.5.STABLE9 and managed sofar to apply all the patches but the 2Gig one to this combination, creating a thing that crashes sometimes 3 times within one hour. For us I am sure that the most of crashes came from the icap patch. Try the latest icap patch (last week) it corrects some of the most often crashes. The latest reports, said that squid-icap was worked for more than 50 hours without problem on a busy proxy server. It is not good but it is better that the 3 times per hour. (After these hours just stopped to talk to the icap server, maybe a problem within the icap server query code, if you are looking for bugs :-) ) However I put it, I am on the loosing end. I could start to write an icap version for S3, but I have also to make that same code run in S2. My opinion is that the icap-client for squid3 must start from scratch. Forget the current code for squid 2. It is problematic. I had thoughts about starting an icap client for squid3 but in practice I have not the time to do. Moreover I believe that this project must start by a person who has a clear view of squid design, in order to prevent in squid3 the problems which has the current squid-icap. For squid2, you have to report bugs and send patches, which corrects some of the problems, until the version for squid3 will be available. For squid 2 maybe I can report some tests which can be done, for someone who looking for bugs in squid-icap and I have in my mind some pieces of code which must be rewritten in order to make squid-icap faster and more stable. Regards, Christos
Re: AW: future of icap-patch
On Tue, 3 May 2005, Baumgaertel Oliver wrote: Well Henrik, that was my point exactly. The problem I have with that is plain and simple. Squid 3 is in development since what, 3 years now? It'll take at least another year to get it into a usable, complete release. Yes. Not the proudest release cycle, but these things happens. Then I'll have most likely to wait another half year until I can introduce it as a test version on one server of the main farm. And then I'll get permission to invest work into it to add the features we need or to fix issues we'll encounter. Then you will always be in a tricky position as your development will be based on a version in freezed state where no new additions will be allowed in. New additions is only allowed in the development phase of the release cycle. After a version has gone into the STABLE state of it's development cycle no new features is allowed in. If you finish your development reasonaly recent after the STABLE1 release then chances are high that it can get quite easily merged into the development version, but the more time which passes after the STABLE1 release the higher the risk that there will be significant amount of work to merge your developments into the current version. But I do not think we will see as large changes as in the Squid-2.X - Squid-3.X in a long while to come. Besides, last time I looked the documentation of 3 was just as bad as the one 2 has. Squid-3 has somewhat better documentation than Squid-2 as each section restructured has had it's documentation updated/written, but there obviously is large gaps. However I put it, I am on the loosing end. I could start to write an icap version for S3, but I have also to make that same code run in S2. Perhaps I can give persuading my employer another shot to go with the current version as is and letting me concentrate on S3 as I originally intended in the first place. But given the current time frame I'd have a better chance to get the clearance for a complete own proxy project. To put things simple: Squid-3 needs more people looking at it for Squid development to move forward in a reasonable pace. Frankly until this happens we are all at the loosing end. The current state is that the main Squid project is currently 2 persons working actively some hours a week, one on Squid-3 (Guido) and one on Squid-2.5 (myself) plus some persons working an hour here or there. Then there is a handful independent developers working on a certain development feature of their interest. Regards Henrik
Cache dir objects to mysql
Hi all! I'm making a little program witch enumerates squid cache directory and puts all urls (fetched from cache objects) into mysql database I noticed that there is 0x3B bytes of data at the begin of every object and it is exactly 0x3B bytes for all objects (I didn't look at the squid source) is that right. The problem is that I can't get object size. My program gets 2 sizes from cache object. First is from Content-Length header if any (-1 if no length header) Second will be difference betweem total object size (file size) and size of overhead. my question is: is there any other overhead after the header ends (after two /r/n). I know that it's better to have a look of source code, but I need some hints. Thanks in advance.
Re: AW: future of icap-patch
Baumgaertel Oliver wrote: Same procedure as last time... It won't patch against the normal STABLE9 branch. What is exactly what I was talking about in the first place. It's no use if we can't run the patch at least against ones that were already introduced some time ago... Ok, but this happens because the icap patch was not stable enough when the STABLE9 was released (still is not) , so it was not make sense to produce a squid-icap-2.5-STABLE9 version because it does not work well. Since STABLE9 was released I corrected a number of bugs, and it was not easy for me, I am not as experianced are the other squid developers, here. In the other hand we must follow the squid development, when the icap patch will be stable maybe the squid has reach the STABLE55 release.. The new version for squid planned for 8 May. If the icap patch looks enough stable, we can freeze a patch release for squid-icap, and why not, make a squid-icap-2.5.STABLE10.tgz file distribution. .And the only way around that is to get it into the main branch. As long as we need the main part of the time to get it into the current code at all it's not possible to really improve its condition. Henrik explained to us the development status of squid. I want to see an icap client in squid3. If someone starts the development of it, I will try to help. But, for my point of view, this is the only I can do in this phase Regards Christos
