Hi Amos,
At 05.06 17/08/2007, Amos Jeffries wrote:
I have just imported and properly wrapped the libesmtp getaddrinfo and
supporting implementation from fetchmail 6.3.8.
I have done some simple configure and compile tests here. Its time to
pass
it back to you Guido for the win32 test.
I
Hi Amos,
At 07.25 15/08/2007, Amos Jeffries wrote:
Hi Amos,
Not good news here ... :-(
We have a problem:
You have used getaddrinfo() and freeaddrinfo() functions, but on
Windows they are available only starting from Windows XP. This means
that your code, even if compiled
Hi Amos,
At 00.13 15/08/2007, Amos Jeffries wrote:
Hi Amos,
Not good news here ... :-(
We have a problem:
You have used getaddrinfo() and freeaddrinfo() functions, but on
Windows they are available only starting from Windows XP. This means
that your code, even if compiled without IPv6
Hi Amos,
At 07.25 15/08/2007, Amos Jeffries wrote:
Hi Amos,
Not good news here ... :-(
We have a problem:
You have used getaddrinfo() and freeaddrinfo() functions, but on
Windows they are available only starting from Windows XP. This means
that your code, even if compiled
On tis, 2007-08-14 at 13:41 +0200, Guido Serassio wrote:
I'm not sure if the licensing of the implementation coming from the
PostgreSQL allow its usage in Squid.
Looks fine. PostgreSQL is licensed under the modified/modern
three-clause BSD license, which is fully GPL compatible.
Hi Amos,
Not good news here ... :-(
We have a problem:
You have used getaddrinfo() and freeaddrinfo() functions, but on
Windows they are available only starting from Windows XP. This means
that your code, even if compiled without IPv6 support, cannot run on
Windows 2000.
I'm also not
Hi Amos,
Not good news here ... :-(
We have a problem:
You have used getaddrinfo() and freeaddrinfo() functions, but on
Windows they are available only starting from Windows XP. This means
that your code, even if compiled without IPv6 support, cannot run on
Windows 2000.
I'm also not
: Re: IPv6 support
I know this may not be completely relevant to the ipv6 discussion, but you
buy a lot of flexibility if you abstract out the socket API /usefully/.
You're then able to do the following:
* easily deal with the different crack unices have when twiddling
socket stuff (eg, via
Henrik Nordstrom wrote:
On Thu, 24 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
Also, it would be nice if Henrik could start with some comments he
said to have on these first IPv6 steps. :-)
I am still here ;-)
The main comment is that we should try to cut down on the number of
#ifdefs. I prefer
On Thu, 3 Mar 2005, [ISO-8859-1] Xuân Baldauf wrote:
The #if ENABLE_IPV6 conditions are to provide a more smooth transition to
enabled IPv6 support. The idea is: When ENABLE_IPV6==0, then everything is
as before. But when ENABLE_IPV6==1, every variable and every struct which
refers IPv4
I know this may not be completely relevant to the ipv6 discussion,
but you buy a lot of flexibility if you abstract out the socket
API /usefully/. You're then able to do the following:
* easily deal with the different crack unices have when twiddling
socket stuff (eg, via ioctls, grabbing the
Alex Rousskov wrote:
On Tue, 2005/02/15 (MST),
[EMAIL PROTECTED] wrote:
I'm trying to bring forward IPv6 support of squid.
FYI: You can try to use Web Polygraph to test performance aspects of
IPv6 support in Squid. For example, it may be useful to compare IPv4
and IPv6 performance (with or
On Wed, 16 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
Further investigation showed: nearly all my IPv6 changes were not distributed
into the squid-ipv6 branch, but into the HEAD branch.
Ok. What probably happened was the same as for the Root, only the top
level directory was correct.
No harm
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
I'm trying to bring forward IPv6 support of squid. I have created a
patch (see http://www.squid-cache.org/bugs/show_bug.cgi?id=1026 ).
Henrik Nordstrom recommended to subscribe squid-dev@squid-cache.org in order
to discuss this
patch, so here
Henrik Nordstrom wrote:
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
I'm trying to bring forward IPv6 support of squid. I have created a
patch (see http://www.squid-cache.org/bugs/show_bug.cgi?id=1026 ).
Henrik Nordstrom recommended to subscribe squid-dev@squid-cache.org
in order to
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
Odd.. you should have write permission.
What repository root did you use?
grep . CVS/Root CVS/Repository CVS/Tag
CVS/Root:[EMAIL PROTECTED]:/cvsroot/squid
CVS/Repository:squid3
CVS/Tag:Tsquid3-ipv6
Maybe I have checked out at a directory
Henrik Nordstrom wrote:
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
Odd.. you should have write permission.
What repository root did you use?
grep . CVS/Root CVS/Repository CVS/Tag
CVS/Root:[EMAIL PROTECTED]:/cvsroot/squid
CVS/Repository:squid3
CVS/Tag:Tsquid3-ipv6
Maybe I have
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
I think I found the reason: The CVS/Root file of the top level directory
was correct, but the CVS/Root file of the lower level directories were not
changed by the cvsmkbranch script.
cvsmkbranch does not change any CVS/Root files, but never
Henrik Nordstrom wrote:
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
I think I found the reason: The CVS/Root file of the top level
directory was correct, but the CVS/Root file of the lower level
directories were not changed by the cvsmkbranch script.
cvsmkbranch does not change any
Xuân Baldauf wrote:
Henrik Nordstrom wrote:
On Tue, 15 Feb 2005, [ISO-8859-1] Xuân Baldauf wrote:
Odd.. you should have write permission.
What repository root did you use?
grep . CVS/Root CVS/Repository CVS/Tag
CVS/Root:[EMAIL PROTECTED]:/cvsroot/squid
CVS/Repository:squid3
20 matches
Mail list logo
