Re: hit a serious blocker on windows

On 10/08/11 01:16, Kinkie wrote:
> hm...
>
> http://msdn.microsoft.com/en-us/library/ms741565%28v=vs.85%29.aspx
>
> However it's a completely different implementation concept, for which
> probably we don't have an abstraction :\
>

Aha. That would be it :).

The CMSG stuff is just for serializing details like those
WSAPROTOCOL_INFO structures, whole cachemgr report pages, etc. into
UDP-like packets over a unix socket. That can be done with a Packer over
TCP or UDP to localhost just as easily. As long as the receiving process
is in the same OS environment it should work.

Amos

> On Tue, Aug 9, 2011 at 2:27 PM, Amos Jeffries<squid3_at_treenet.co.nz> wrote:
>> On 09/08/11 23:59, Kinkie wrote:
>>>
>>> Hi all,
>>> I've hit a bit of a problem in mswindows porting: IPC uses Unix
>>> domain sockets, which are not available on windows.
>>>
>>> In order to proceed, I believe that we need the help of Alex to
>>> understand whether other socket families can be used in his opinion,
>>> and of Guido to understand what alternatives we may have on Windows to
>>> send messages around..
>>>
>>> Could you guys speak up?
>>>
>>> Thanks
>>>
>>
>> I recall learning years ago about a Windows alternative that might be usable
>> here for passing socket handles. But I fail to remember exactly what it is.
>>
>> Everything else SMP uses the channels for can be duplicated with TCP
>> sockets. Open a TCP socket saving its IP:port details, fork the child,
>> connect() from child to the parents socket address. AFAICT squid ipcCreate()
>> already tries to do this when the it is told to use TCP.
>>
>> Amos
>> --
>> Please be using
>> Current Stable Squid 2.7.STABLE9 or 3.1.14
>> Beta testers wanted for 3.2.0.10
>>
>
>
>

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.14
   Beta testers wanted for 3.2.0.10