mod-xslt-devel

[mod-xslt-devel] Re: mod-xslt

[Philipp D. <ph...@du...>]

Hi there,

sorry, it's not sourceforge, it's me. I have been working day and night
on my thesis and have not spent a lot of time on mod-xslt.
I just checked the stuff you did. I haven't completely grasped every
single detail yet (didn't check that carefully), but it looks like there
are some great things coming.
I have looked at the code more intensely last Friday. The one thing that
struck me was that it is a gigantic mess that will turn hell to maintain
sometime soon. So I'm thinking of rewriting and cleaning up when I have
some more time. (But I fear, that's no going to be until this summer in
NY)
I will send you a .tgz sometime end of this/beginning of next week. It
is the first part of the 3 part thing I told you about. After this the
only thing that's missing is the PDF renderer.

Aside from all that, I want to create some rules for mod-xslt:
1. All decisions concerning mod-xslt are simple majority decisions
reached by vote.
2. All developers of mod-xslt have the right to vote.
3. For a vote to be valid all have to have notice of the impending vote.
4. Any single developer may veto a vote to be held on an issue and
demand further discussion on the issue.
5. If a majority cannot be reached, discussion has to be continued until
a majority can be achieved.

What does this mean, you can make decisions on mod-xslt just as well as
I can. But before doing so, send mails telling me what you want to do.
You do not need to ask me if it's ok, you do not need to wait for an ok
from me. All you need to do is tell me.

TTY Philipp

On Wed, 2003-02-19 at 22:37, Gennady Feldman wrote:
> Hi Philipp,
> 
> I am not sure what's happening with you lately. It seems like
> SourceForge was offline for some time and I am not sure if you received
> any of my e-mail messages. Just to re-cap, I have checked-in everything
> I have into the HEAD branch of CVS (did you get a chance to look at
> it?), and I have created/updated a separate branch for the MOD_XSLT_1_0
> series.
> 
> P.S. Waiting patiently for your reply :)
> 
> G.F. aka Gena01
> http://www.gena01.com
-- 
--------------------------------------------------------------------
Any connection between your reality and mine is purely coincidental.
--------------------------------------------------------------------
Philipp Dunkel <ph...@du...>
--------------------------------------------------------------------

Re: [mod-xslt-devel] Re: mod-xslt

[Philipp D. <ph...@du...>]

Hi G.,

[snipped]
> > I will send you a .tgz sometime end of this/beginning of next week. It
> > is the first part of the 3 part thing I told you about. After this the
> > only thing that's missing is the PDF renderer.
exins: Creates xml dynamically (could be used to build a very fast CMS)
via an xml-based language
xslt: (What we have been working on)
pdf: Make PDF from xsl-fo to in a webserver module.
This would be a perfect base for a CMS or any other web project

[snipped]
 
> Also:
> - we should disable external references in our module, esp if we want
> to do the transformation. The whole thing should be self-contained. It 
> will also give us an opportunity to finish If-Modified-Since code and
> will simplify things. What do you think of this?
I disagree, because external references are afaik resolved automatically
by libxml2/libxslt. I would just ignore them for If-Modified-Since.
There needs to be some responsibility left for the webmaster. All he'd
need to do is touch the main file to clear the cache. I think external
references may have more value than this extra hassle.
(This is what I call a RFD {Request for Dispute})
> - We need some cleanup of the code and and to remove any dead code that
> we don't need.
Definitely
> - We need to add some thread safety code and make sure we are not
> leaking
> anything. 
Definitely, but thread safety is not a matter of adding things, it's a
matter of cleanup! Any access to global variables will kill thread
safety. We also need to check if libxml2/libxslt are even thread safe.
> At this point I am trying to stabilize most of my changes and will
> try to have it pretty stable and start to heavy test this by the end of
> the
> week. My reason for this is that I need to have a frozen version to 
> test/setup on other server(s) at work. 
Feature Freeze is right up my alley. For my tastes, mod-xslt should do
one thing and do it well. Any more features and it will suffer from
bloat.
There have been times, when I even thought of removing the whole
parameter and cookie thing and simply stick to XSLT and XSLT alone.
But since Parameters are part of the spec, I figured they might be worth
it.
> Should I add #defines for my stuff?
No
[snipped]

TTY Philipp
-- 
--------------------------------------------------------------------
Any connection between your reality and mine is purely coincidental.
--------------------------------------------------------------------
Philipp Dunkel <ph...@du...>
--------------------------------------------------------------------