Hi Jem,
Le Dimanche 3 Juillet 2005 05:18, Jem Berkes a écrit :
I'm just getting into module development for the first time (thanks to
impetus provided by Google's Summer of Code)... I've got a test
environment with 2.1.6-alpha and have succeeded in writing minimal modules
and getting them
Roy T.Fielding wrote:
On Jul 2, 2005, at 7:46 PM, Maxime Petazzoni wrote:
The first thing that has to be done is, of course, get rid of the hard
coded HTML and switch to something more flexible.
Careful with getting rid. I haven't looked at it myself, but I wonder
if cleaning it up and
Roy T. Fielding wrote:
On Jul 2, 2005, at 7:46 PM, Maxime Petazzoni wrote:
The main goal of my SoC project is to enhance mod_mbox's interface by
using newer web development techniques and/or technologies, while
avoiding any noticeable slowdowns.
That's good, but keep in mind the general
Hi,
I believe the core goal is separation of data from presentation. The
standard reply is to use some kind of template language. A glue. Let
it be PHP, XSLT, ClearSilver, or any of the other hundreds out there.
Why do we want glue?
I believe that XHTML, no matter how masterfully
I'm just getting into module development for the first time (thanks to
impetus provided by Google's Summer of Code)... I've got a test
environment with 2.1.6-alpha and have succeeded in writing minimal modules
and getting them working on a live server. But I have a few nagging
questions that I
Jem Berkes wrote:
For example, for SMTP support we are contemplating the protocol unit
(mod_smtpd) passing on mail to a module that specifically delivers mail.
How do those two entities communicate with each other? A
mod_smtp_deliver would get a potentially large chunk of data (const
char* ?)
... The other solution (letting mod_smtpd read the whole
thing into a buffer and then passing the buffer) seems way too memory
hungry for me.
I was trying to figure that out too. It seems like a bad idea to read the
whole thing into memory because the buffer could easily require several
tens
On Jul 3, 2005, at 1:29 AM, Paul Querna wrote:
I believe the core goal is separation of data from presentation.
No, the core goal is to provide an ultra-efficient interface to
large mail archives. The data is already available in mbox form.
The standard reply is to use some kind of template
On Jul 3, 2005, at 4:18 AM, Maxime Petazzoni wrote:
+1. XML has the particularity to describe only the data, as opposed to
XHTML which stores data *and* structure information.
No, XML is a data structuring (mark-up) metalanguage. The only
difference between arbitrary XML and XHTML is that
Sergio Leonardi wrote:
Hi all
I'm a newbie and I'd like to plan to add to mod_cache a directive like this
one, if possible.
What could be the correct procedure to do it? Am I sending the message to
the wrong place?
Hi Sergio.
It sounds like a great idea.
How do you plan on implementing
I've been playing with basic modules that implement their own protocol
(process_connection hooked) along the lines of the mod_echo example. But
one thing I can't seem to do is send output immediately back to the client,
even though I am flushing the output filters.
With the following code, if
I don't see why it matters if there are redundant members in
request_rec. However, for purity, it might be cool to divide
request_rec up into common elements and protocol-specific stuff in a
union.
That's not really a problem, though of course it's hacky. It's the
logical consequence
Jem Berkes wrote:
I've been playing with basic modules that implement their own protocol
(process_connection hooked) along the lines of the mod_echo example. But
one thing I can't seem to do is send output immediately back to the client,
even though I am flushing the output filters.
With
What is your Listen line for this protocol's port?
I just had Listen 1234
Try something like:
Listen 0.0.0.0:1234 myproto
AcceptFilter myproto none
Well that did indeed solve my problem :) Thanks.
I wrote a little mod_rdate if anyone is interested,
http://www.sysdesign.ca/archive/apache/module-experiment/mod_rdate.c
rdate allows a host to synchronize its time to a server, with approximately
1-second accuracy. It is far inferior to NTP but so much simpler and still
my preferred method for
On Jun 27, 2005, at 7:16 AM, William A. Rowe, Jr. wrote:
Thoughts?
+1 on all items.
S.
--
[EMAIL PROTECTED] http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF
smime.p7s
Description: S/MIME cryptographic signature
16 matches
Mail list logo
