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
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
Hi,
As you probably already know, a couple of students will be working on
ASF projects during the summer within Google's Summer Of Code
program. I have the chance to being one of the few selected for this
adventure, and I will be working on improving mod_mbox's interface.
Members of the mod_mbox
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 design principle to
avoid
