From: Pit Capitain <pit@...>
Date: 2001-09-19T04:22:41+09:00
Subject: [ruby-talk:21346] Re: iowa and win98

On 18 Sep 2001, at 23:04, Avi Bryant wrote:

> On Tue, 18 Sep 2001, Horst Rischbode wrote:
> 
> > Hi,
> > 
> > I'm trying to build a running development environment on my
> > Win98-Laptop including apache and iowa. 
> > 
> > That's what I have done:
> > - Installed cygwin
> > - Installed apache
> > - Tested apache
> > - Downloaded iowa
> > 
> > Following Avi's instructions coming with iowa or the instructions of
> > the apache-people within their DSO-documentation leads me to the
> > same problem while building the iowa-module.
> 
> Instead of the module, you might just use the iowa.cgi script instead
> - it should be less hassle on Win98 than dealing with apxs.  The
> comment at the top of the file describes its use.
> 
> Good luck,
> Avi
> 

Hi Horst and Avi,

I recently tried to compile mod_iowa on Win 98, too, using VC++ 
like I did before with my own Apache modules. I had problems with 
the struct sockaddr_un, which isn't defined in my VC++ header 
files.

This socket type seems to create a named pipe which is used to 
communicate between the Apache iowa module and the 
application specific iowa server process. I tried to use a struct 
sockaddr_in instead for the communication but Apache got an error 
in the connect call. I had not more time to investigate so I finally 
used the CGI script as Avi suggested.

Still it would be nice to be able to use the Apache module. In Ruby 
I can use class UNIXSocket without problems on my Win 98 
notebook, so somewhere in the ruby or cygwin code there must be 
an implementation of named pipes. If someone knows how to 
compile an Apache module dll using cygwin please drop me a 
short hint how to do it.

Maybe some day there'll be other ways to communicate with the 
iowa servers. What I don't like about the named pipes is that there 
can be no more than one server process per application. We'll 
see...

Regards,
Pit