Re: PATCH: Cygwin: file mode support and ufs writecleanswap bugfix

On Fri, Jan 05, 2001, Robert Collins wrote:
> I believe you may have meant to cc this back to the list? I recall Henrik mentioning you had a problem with the Reply All button on
> your mail client? (grin).

Yes, I do still have that problem. Oops. :)

> > What would be needed to have it run natively on all three. I haven't
> > hacked windows code for such a long time ..
>
> Have you looked into cygwin? It is native code. Cygwin provides a .dll that the programs are linked to which provides the Unix API.

Yup, I've played with cygwin, but it was a couple of years ago.

>
> > changing. I'd hope that with the modio and commloops work squid
> > would become modular enough to just need "NT modules" (and
> > perhaps some extra bits like a memory allocator..)
>
> Lots of things. I don't agree with them all as a matter of fact (but that's a different topic). The comms calls are wrapped to WSA
> (windows sockets), syslog & daemon mode is disabled, the registry is parsed instead of /etc/resolv.conf for DNS configs, Squid runs
> as a service not a background process. I don't believe the ufs module has _any_ changes for windows (I haven't checked yet either
> :-/ ).

Right.

Well, if the aufs code was implemented as the ufs code wih a replacement
disk.c using the aiops (which is actually looking to be a good idea
right now ..) then the windows "ufs" code could just have a seperate set
of "aiops" which use the event-driven disk stuff I seem to remember.

> The OS/2 code makes the number of changes relatively small. There are some optimisations to use async disk calls (provided by the
> win32 API) that would be very useful.
>
> But as I said - I am planning to bring a lot of it over to the 'cygwin' branch anyway. They can coexist. Cygwin provides things like
> syslog that I happen to find _very_ useful, and running as a service is no good for development _OR_ for use on windows 9x/98/ME.
>
> Rob
>

Ok. The point I'm trying to make here is that squid should end up being
modular enough to plug in windows bits or unix bits without #ifdefs
splattered around (yes you'll need them to fix differences in
the implementation of some things, but not to implement completely
new features per-platform.)

Adrian

-- 
Adrian Chadd			"Here's five for the cake, and
<adrian@creative.net.au>	  five to buy a clue."
				    - Ryan, Whatever it Takes