[EMAIL PROTECTED] (Ken Williams) wrote:
>[EMAIL PROTECTED] (Doug MacEachern) wrote:
>>don't know why they're so different, but this looks like part of the
>>problem, since you do have unistd_h
>>i would try changing this part to:
>>
>>#ifndef HAVE_UNISTD_H
>>#define HAVE_UNISTD_H 1
>>#endif
>
>Yea
[EMAIL PROTECTED] (Doug MacEachern) wrote:
>On Thu, 17 May 2001, Ken Williams wrote:
>> They're also in /usr/include/unistd.h , but is the opening #ifndef
>> messing things up, perhaps? (don't know what yours looks like)
>
>no, that's a standard convention so header files don't get included
>more
On Thu, 17 May 2001, Geoffrey Young wrote:
> you mean that when 2.0 sees PerlModule it just checks to see if it's valid
> then (later) perl checks for the module in @INC,
> whereas 1.3 does all this as it happens? Same for (yet to be implemented?)
> custom directives?
well, there is no PerlMod
On Thu, 17 May 2001, barries wrote:
> *click* thanks. "message" != "connection" and "body" != "content" threw
> me off. "body" makes some sense to me, but why "message"?
because an InputMessageFilter filters the whole HTTP message, headers +
body. InputBodyFilter filters only the body. from r
> -Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 17, 2001 11:47 AM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: more Apache::Test stuff...
>
>
> On Thu, 17 May 2001, Geoffrey Young wrote:
>
> > these patches seem to solve
On Thu, 17 May 2001, Jens-Uwe Mager wrote:
> Darwin (aka Rhapsody) always has a 64 bit off_t, there is no small file
> compile environment.
ah, ok. wish that was the case with all platforms!
-
To unsubscribe, e-mail: [EMAIL
On Thu, 17 May 2001, Ken Williams wrote:
> They're also in /usr/include/unistd.h , but is the opening #ifndef
> messing things up, perhaps? (don't know what yours looks like)
no, that's a standard convention so header files don't get included more
that once.
> /* check: #include */
> -#ifn
On Thu, 17 May 2001, Geoffrey Young wrote:
> these patches seem to solve the problem by moving PerlRequire (and
> PerlSwitches?) to the preamble, thus insuring that @INC is modified before
> seeing any extra configuration stuff...
only problem is the patch causes pretty much all of 2.0's test t
On Wed, May 16, 2001 at 08:15:50PM -0700, Doug MacEachern wrote:
> On Wed, 16 May 2001, barries wrote:
>
> > What's the philosophy behind the naming of InputMessageFilter and
> > InputBodyFilter, which seem to correspond to input connection filters
> > (ie for the headers) and input request filte
> -Original Message-
> From: Doug MacEachern [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 11:23 PM
> To: Geoffrey Young
> Cc: '[EMAIL PROTECTED]'
> Subject: RE: more Apache::Test stuff...
>
[snip]
> they are supposed to be in t/conf/modperl_inc.pl (generated by
> Apache::T
On Thu, 17 May 2001, brian moseley wrote:
> On Wed, 16 May 2001, Matt Sergeant wrote:
>
> > Oh, and the section should be called "Application
> > Servers", IMO.
>
> i think "application server" describes a system that does
> more than implementing a templating language.
Yes, that's the idea.
/m
>
> Sure, if you don't mind add a few words about these too:
>
> Mason
> OpenInteract (openiteract.org)
>
Ok, I writre something about Mason too and take a look at OpenInteract (but
I don't know much about it) in the next few days
Gerald
---
On Thu, 17 May 2001, Matt Sergeant wrote:
> On Thu, 17 May 2001, Stas Bekman wrote:
>
> > > > How about http://www.openinteract.org/ which is heavily based on TT.
> > >
> > > Yep, that should go in there too.
> >
> > anything else?
>
> Well you could add *lots* of modules in there, e.g. RAO, Apac
On Thu, 17 May 2001, G.Richter wrote:
> >
> > anything else?
> >
>
> Embperl has become much more then embedding Perl into HTML over the last
> four years. So I would like to move it also down to the toolkit section. If
> nobody has any objection, I would write a few words and commit it to the
>
On Thu, 17 May 2001, Stas Bekman wrote:
> > > How about http://www.openinteract.org/ which is heavily based on TT.
> >
> > Yep, that should go in there too.
>
> anything else?
Well you could add *lots* of modules in there, e.g. RAO, Apache-Template,
Apache-OAS, Apache-iNcom, Zobel... You could/s
>
> anything else?
>
Embperl has become much more then embedding Perl into HTML over the last
four years. So I would like to move it also down to the toolkit section. If
nobody has any objection, I would write a few words and commit it to the
modperl site
Gerald
--
On Thu, 17 May 2001, Matt Sergeant wrote:
> On Thu, 17 May 2001, Stas Bekman wrote:
>
> > > Oh, and the section should be called "Application Servers", IMO.
> >
> > Do you suggest a new section or to rename the one I've created?
>
> Rename.
ok
> > How about http://www.openinteract.org/ which is
On Thu, 17 May 2001, Stas Bekman wrote:
> > Oh, and the section should be called "Application Servers", IMO.
>
> Do you suggest a new section or to rename the one I've created?
Rename.
> How about http://www.openinteract.org/ which is heavily based on TT.
Yep, that should go in there too.
> e
On Wed, 16 May 2001, Matt Sergeant wrote:
> On 17 May 2001, [EMAIL PROTECTED] wrote:
>
> > +
> > +
> > + http://template-toolkit.org/";>The Template
> > + Toolkit is a fast, powerful and easily extensible
> > + template processing system writt
On Wed, May 16, 2001 at 08:09:05PM -0700, Doug MacEachern wrote:
> On Tue, 15 May 2001, Ken Williams wrote:
>
> > Is the suggestion below, about building Apache with -D_LARGEFILE_SOURCE,
> > accurate? That flag seemed to have no effect when I used it in building
> > Apache, and I couldn't find a
On Wed, 16 May 2001, Matt Sergeant wrote:
> On 17 May 2001, [EMAIL PROTECTED] wrote:
>
> > +
> > +
> > + http://template-toolkit.org/";>The Template
> > + Toolkit is a fast, powerful and easily extensible
> > + template processing system writt
21 matches
Mail list logo
