I want join squid-dev mailing list

2007-01-08 Thread Fajri Kurniawan
Hello,

My name is Fajri Kurniawan, I am from indonesia.
I'm an undergraduate student. I join this mailing list because I want to
know about developing plugin in Squid.

I have no experience using Squid. But I have some experience in C++
programming. I'm working for my final project.

Thanks



information request

2007-01-08 Thread foomail123
Hi,

I am using SQUID-3.0 develop version.
I see 3.0 is a rewrite of 2.x and in C++.

Question:
I see:
10223345 Jan  8 11:07 src/squid
on x86, Linux 2.x.

I am looking for a way to make the image footprint
as small as possible. I need *only* proxy
functionality.

Is there a way to disable caching code (and others)
except proxy, via the configure script etc ?
Can I use more dlls etc. ? Any suggestions to get
a small image ?

Thanks !

Sk

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


Re: Debug

2007-01-08 Thread Henrik Nordstrom
mån 2007-01-08 klockan 17:27 +1300 skrev Amos Jeffries:

 The problem I am tracking is a DNS timeout when a TCP_MISS:DIRECT begins 
 but can't figure out how to get any action-by-action or 
 function-by-function record of what calls are being made in the area.

Well. it is not so easy. Squid is effectively one big state machine
centered around the comm loop.  While it's waiting for an external event
(network I/O mainly) there is no code only state..

Assuming it's an address lookup failing then the two most important
entry points to look as is ipcache_nbgethostbyname and idnsGrokReply.

ipcache_nbgethostbyname is the entry point to the DNS code for looking
up the address of a host name.

idnsGrokReply is where the raw DNS responses is processed and results
handed back to the module which asked for it..

ipcache_nbgethostbyname to the point where the DNS query is ready to be
sent should be normal linear code.

idnsGrokReply is all linear code up to an including the callback to the
module which initiated the DNS query (i.e. all the way to the forwarding
code when the query came from there.). But there is one or two callbacks
before the forwarding code is reached so it's perhaps not entirely
obvious if only reading code.

Regards
Henrik




signature.asc
Description: Detta är en digitalt signerad	meddelandedel


Re: I want join squid-dev mailing list

2007-01-08 Thread Henrik Nordstrom
mån 2007-01-08 klockan 11:43 +0700 skrev Fajri Kurniawan:

 My name is Fajri Kurniawan, I am from indonesia.
 I'm an undergraduate student. I join this mailing list because I want to
 know about developing plugin in Squid.

Welcome!

 I have no experience using Squid. But I have some experience in C++
 programming. I'm working for my final project.

Interesting. Can you describe a little of what it is you are working on?

Regards
Henrik


signature.asc
Description: Detta är en digitalt signerad	meddelandedel


Re: Debug

2007-01-08 Thread Amos Jeffries

Henrik Nordstrom wrote:

mån 2007-01-08 klockan 17:27 +1300 skrev Amos Jeffries:

The problem I am tracking is a DNS timeout when a TCP_MISS:DIRECT begins 
but can't figure out how to get any action-by-action or 
function-by-function record of what calls are being made in the area.


Well. it is not so easy. Squid is effectively one big state machine
centered around the comm loop.  While it's waiting for an external event
(network I/O mainly) there is no code only state..


I'm getting to see the picture as clearly an opaque problem. ;-)

Over the last two days. The more I work on this the more I wish there 
was some developer documentation saying things like this clearly 
available in the source or on the website. So newbies like myself can 
quickly get a picture of where to look for the entry points to all the 
events without having to ask.





Assuming it's an address lookup failing then the two most important
entry points to look as is ipcache_nbgethostbyname and idnsGrokReply.

ipcache_nbgethostbyname is the entry point to the DNS code for looking
up the address of a host name.

idnsGrokReply is where the raw DNS responses is processed and results
handed back to the module which asked for it..

ipcache_nbgethostbyname to the point where the DNS query is ready to be
sent should be normal linear code.

idnsGrokReply is all linear code up to an including the callback to the
module which initiated the DNS query (i.e. all the way to the forwarding
code when the query came from there.). But there is one or two callbacks
before the forwarding code is reached so it's perhaps not entirely
obvious if only reading code.

Regards
Henrik



Stranger, and stranger.

Thank you for those entry points. I found the idnsGrokReply after much 
random code reading yesterday and found it doing something.
Also, the error has moved further down the sequence now from DNS timeout 
to connection timeout (to localhost apache!). Without any code changes 
on my part. I'm going to have to trace the traffic in my environment I 
think to see exactly what its asking for before I get further into the 
code. :-(



Amos


Re: Debug

2007-01-08 Thread Henrik Nordstrom
tis 2007-01-09 klockan 13:30 +1300 skrev Amos Jeffries:

 Over the last two days. The more I work on this the more I wish there 
 was some developer documentation saying things like this clearly 
 available in the source or on the website. So newbies like myself can 
 quickly get a picture of where to look for the entry points to all the 
 events without having to ask.

Some of this is actually in the programmers guide. 
ipcache_nbgethostbyname is at least..

but very very much is missing. The programmers guide got started many
years after most of the code had been developed, and focus has been
mostly on documenting the areas changed/redone..

Personally I'd like to see the little we have in terms of programmers
guide translated to doxygen and moved down to the appropriate modules.
Would hopefully make it more natural to write and maintain the code
module documentation.. But that's a different project.

Regards
Henrik


signature.asc
Description: Detta är en digitalt signerad	meddelandedel