I'd be happy to help out. I know Jörg is interested, as well, so,
please, let's hear from everyone before we jump into any kind of voting.
-kip
.
Matt Sergeant wrote:
Guys,
I know you're not generally responsive to axkit-dev posts, but this is
pretty important as it has a cut-off date (31st Jan)
Matt Sergeant wrote:
OK, so committers please vote for PMC membership now for:
I'm not sure how appropriate it is to vote for one's self, but, in the
interest of completeness...
[ ] Matt Sergeant
+1
[ ] Kip Hampton
+1
-kip
Matt Sergeant wrote:
- Fix the cache delivery system and clean up this whole area.
- Add two new language processors - XML::STX and PeTaL.
- Get it working with Apache::Fake (Jorg don't you dare commit these
changes yet ;-)
- Fix config merging (I believe Kip is working on that)
More writing that
Howdy AxHackers,
Feature:
Add a get_dom() method to the Providers to allow custom Provider authors
to pass in an XML::LibXML DOM document instance.
Justification:
Currently, application-based Provider authors must either:
1) incur the major overhead of calling toString() on their DOMs and
return
Feature:
Add an AxKit configuration directive that allows users to skip over the
get_styles() root, DTD stylesheet PI extraction as needed.
Justification:
The AxAdd(Root|DTD|Doctype)Processor directives are damn useful for most
general cases, but users should have the option to skip over the log
Jörg Walter wrote:
On Monday, 17. February 2003 04:27, Kip Hampton wrote:
Feature:
Add an AxKit configuration directive that allows users to skip over the
get_styles() root, DTD stylesheet PI extraction as needed.
We could make that automatic - we know at request time if any
content-dependent
Robin Berjon wrote:
Jörg Walter wrote:
On Monday, 17. February 2003 04:08, Kip Hampton wrote:
Feature:
Add a get_dom() method to the Providers to allow custom Provider authors
to pass in an XML::LibXML DOM document instance.
Look at LibXSLT.pm for example - the code used to parse the XML is
used
Matt Sergeant wrote:
> Or are you saying
the other way around - provide a default get_dom() that works on top of
the current get_fh() and get_strref() implementations? That makes a lot
of sense to me.
Right, he means just a wrapper over get_strref() and get_fh() that
DOM-returning subclasses cou
Howdy AxDevers...
I think I've stumbled over a subtle logic flaw in AxKit.pm's
main_handler method as it relates to Providers and caching. The
"problem" lies in the fact that the Provider's process() method is
called before determining whether or not the resource is cached.
The Provider's proce
Jörg Walter wrote:
On Thursday, 13. March 2003 22:53, Kip Hampton wrote:
Howdy AxDevers...
I think I've stumbled over a subtle logic flaw in AxKit.pm's
main_handler method as it relates to Providers and caching. The
"problem" lies in the fact that the Provider's process(
Matt Sergeant wrote:
On Thu, 13 Mar 2003, Kip Hampton wrote:
So I'm happy for you to do whatever is required as long as it doesn't
break regular file use.
Agreed.
Plus you can probably use the current AxKit::Cache
module for doing provider level caching.
Yup, any other way would silly
Chris Leishman wrote:
Really? I didn't notice that... AFAIK a Content-Length header is only
actually returned when delivering from a cache file (apache calculates
the content-length, etc, after the $r->filename is set and the handler
declines). When delivering normally I noticed that there is
Howdy AxDevers,
Okay, I finally had a chance to install the proposed caching patches
that came from Chris L through the users' list (CC'ing you, Chris since
I'm not sure if you're subbed here or not). The changes proposed touch a
fair amount of code and re-organize some of AxKit most basic behavio
Matt Sergeant wrote:
I just need votes now on whether or not to apply the fix. Can I see a show
of hands?
+1
-kip
Robin Berjon wrote:
They don't care about being compatible with us. In fact, just because
it's suggested by one of us and not one of them they'll reject it as
"dirty". I'd say don't bother wasting your patience on them.
You may be right, but that doesn't mean we shouldn't try. If they're
wrong
Matt Sergeant wrote:
I'm going to release 1.6.2.
OK?
+1 Though I'm concerned that the new Apache::Test stuff will make
installing via CPAN a real PITA (unless the right httpd is in the path,
the tests can never pass). Thoughts there?
-kip
Ignore
[EMAIL PROTECTED] wrote:
jwalt 2003/09/17 14:58:39
Modified:.Changes Makefile.PL
lib/Apache/AxKit LibXMLSupport.pm Provider.pm
lib/Apache/AxKit/Language XPathScript.pm
lib/Apache/AxKit/Provider File.pm FileWrite.pm
Log:
- create p
Jörg Walter wrote:
On Friday, 19. September 2003 09:57, Matt Sergeant wrote:
Since it broke the test suite, can you back out the change and check it
in on a branch. Thanks.
I can easily back out the change in XPathScript, as it is the only module not
working. The others work well even on several
Jörg Walter wrote:
Am Tuesday, 23. September 2003 09:39, schrieb Matt Sergeant:
Is there any value in making the pre-load module a separate module on
CPAN?
Given that Preload.pm essentially only is 10 lines + docs, probably not...
+1 to putting it in the core dist.
-kip
After careful thought, I'm still of two minds about the advisability of
doing URI-scheme bindings inside AxKit.
On the one hand, I think users would greatly benefit from having things
like document('xmldb://whatever/query') "just work" from within XSLT and
XPathScript stylesheets, but I can't h
What:
Extend attribute-value-template behavior to include the 'name' attribute
for XSP's and .
Why:
Syntactic sugar, really. We now offer AVT for attribute values in
literal output, so, why not have it for the generated names of elements
and attributes created via and to save
users a bit of verb
Matt Sergeant wrote:
And the "value" attribute for xsp:attribute.
Funny, I thought about this originally, too, but there's no such animal.
XSP's 'attribute' element has the same behavior as XSLT's[1]. That is,
the value for the newly created attribute may appear only as the text
contents of the
Matt Sergeant wrote:
We're the only project lagging on this (aside from Xerces-P, which is in
a similar boat). It's not a big deal for us, I think, because we have
CPAN. But I think we should do it anyway.
Can one of the committers figure out what needs doing and how?
I'll do it tonight (Monday)
I wrote:
I'll do it tonight (Monday).
Okay, mostly done.
All that's left is for Matt to create a KEYS file in
/www/www.apache.org/dist/axkit/ (on minotaur) with his public key in it
so folks can use the .asc file to verify the download (here's an example
[1] ).
Past that, all redirects, symlinks,
Matt Sergeant wrote:
OK, think I did it. No idea if there's something you can do to syntax
check the file though...
I just imported them without a hitch and verified your sig for the
current distribution. I'd say that we're all set.
-kip
Matt Sergeant wrote:
In case some of you on here aren't subscribed to general@xml.apache.org,
I suggest you either subscribe now or go through the archives. They are
talking about re-partitioning the XML PMC, and this might quite
drastically effect how the AxKit project is managed. Your feedback
Hey Folks,
The Apache licence has now officially changed to the 2.0 version and we
need to update our stuff accordingly. I say we take the opportunity to
round up bugsfixes and other patches and get them ci'd in preperation
for a new release.
Votes?
Also, Matt, can you *please* change the downl
Matt Sergeant wrote:
All done now.
Thanks, daddy-o.
-kip
Matt Sergeant wrote:
I don't think there's much to go in, but essentially I'm +1.
Its not like we have showstoppers and need to do a mad dash or anything,
but I do think its important that we get the licensing in the dist
updated and I know that some of us (me) have the tendency to let little
th
Mike Chamberlain wrote:
Namely..
The changes to provider.pm and AxKit.xs which fix the get_strref called
twice bug.
The changes to the way error styles are handled (Provider::Error + some
changes to AxKit.pm)
which makes error styles work with AxMedia
+1 on both
-kip
Michael A Nachbaur wrote:
This adds a new configuration directive "AxDirHandler " which is
used to indicate the desired directory handler plugin, but AxHandleDirs
On|Off is still required to toggle if directory listings will be
handled. If AxDirHandler is not specified, the default module
Ap
Can someone wake the hamster that powers axkit.org
Maybe we need to rethink hosting?
-kip
Hey guys,
We really need to clear up the problem w.r.t. Contributor License
Agreements that are still missing for some of the AxKit committers. The
remaining culprits are:
Robin Berjon
Barrie Slaymaker
Joerg Walter
Even if you don't think you'll be contributing code to AxKit in the
future, if y
Matt Sergeant wrote:
I'm personally in no hurry to do this, but it depends what the community
thinks.
I'm in no rush, either. There are several things to consider:
First, we've chosen not to use the resources provided by the ASF so that
we can publish AxKit's public site *using* AxKit. I still thi
Howdy Folks,
This message is a long time coming and, since no one seems to want to
step up to address the issue I guess I'll be the one to drag in into the
light...
Specifically, I'm concerned about apparent lack of recent interest in
AxKit among what have historically been its core developers
Mike Chamberlain wrote:
I like the idea of having a Pumpkin, I think the problem we've been
having recently is no one has been wanting to take charge, and at
other times too many people want to run the show / have conflicting
ideas and there isn't anyone who is willing to act as a chairman to
get
Matt Sergeant wrote:
On 6 Apr 2004, at 17:13, Kip Hampton wrote:
[1] http://totalcinema.com/axkit/axkitguidelines.xml
I think this document hits the mark, and I'm +1 on moving forward with
becoming a TLP and adopting this new development approach. I've gone
over this document twi
Matt Sergeant wrote:
Chris reports progress to the AxKit PMC at the (newly instituted)
bi-weekly dev meetings.
When the items on Chris' RP are knocked down and released, the process
starts over.
This seems like the Pumpking is also going to be the main developer on
the release.
Not necessaril
Matt Sergeant wrote:
We need to come to a decision on this - whether to fundamentally change
our pipeline model in AxKit-2.0.
I think the only sane answer to "do we do implement a pull or a push
model for the core pipelines?" is "Yes!". What I mean is: why don't we
make the pipeline just YA swap
Matt Sergeant wrote:
My suggestion is that to move forwards with things we hold off on the TLP
thing for now - lets get the other parts of Kip's proposal working first.
Lets try and eat this sandwich a bite at a time.
Any objections/comments?
Part of the point of the TLP proposal was to snap people
Matt Sergeant wrote:
I was just afraid that we could have problems eating the whole sandwich
if it just looks like too much to take on.
Sure, understood. I just truly believe that this is one of those cases
where we'd do better to just dive in and take things as they come.
-kip
Matt Sergeant wrote:
Hope you like the addition of the URL. I think it makes spam a lot
easier to fix.
Yeah, its a big help... one of those "I can't believe we didn't think of
it before" things.
-kip
Sorry for the lag... busy-busy...
Matt Sergeant wrote:
OK, well Berin's asking about progress on the PMC list. Would you like
to respond or would you prefer I did?
Either way is fine with me. I don't mind doing it, but it'll have to
wait till Mon. or Tues.
-kip
Matt Sergeant wrote:
OK uploaded. (the pb is in the img/ folder if you want to access it).
Cool. Thanks, man.
The stylesheet just changed the title bar height - is that what you
expected?
Yep, the header just needed to get a little taller to accommodate the
new logo graphic.
What do you think ab
Matt Sergeant wrote:
OK uploaded. (the pb is in the img/ folder if you want to access it).
http://axkit.org/img/pb_axkit.png gives me a 404
-kip
David J Craigon wrote:
What I really want to see
is the XML that failed to parse in the first place so I can identify the
problem. Is there any way of achieving this?
Yes, but not using AxTraceIntermediate (the mechanism for which is only
invoked after the source XML is parsed, so an error ther
Howdy folks,
Just two things left to do before the ASF Board can decide whether or
not AxKit will become a Apache TLP (Top-level Project). They are:
1) Gather volunteers for the proposed Project Management Committee
(PMC). and vote on a PMC Chair from among those volunteers.
2) Draw up the offi
Matt Sergeant wrote:
And I gladly +1 you both, happy to take a back seat. While I still love
this project I'm clearly not helping things along much these days by
trying to lead it by not doing anything.
Well, I know I'd feel better if you'd sit on the PMC, if only in an
advisory role-- but its u
Michael A Nachbaur wrote:
Essentially, this patch intends to add the "AxXMLCatalog" Apache directive
which defines which XML catalogs to include into XML::LibXML.
Might we not be better off creating a more generic AxXMLParserOpt
directive (that pushes onto a @list of key/value pairs)?
Rationale
Michael A Nachbaur wrote:
So, if this is the direction everyone'd like to go (anyone?) the XML Catalog
directive would look like so:
AxXMLParserOpt XMLCatalog /catalog1.xml
AxXMLParserOpt XMLCatalog /catalog2.xml
AxXMLParserOpt MaxDepth 4500
etc...
+1
Matt Sergeant wrote:
OK, I feel the love :-)
Yay!
Right, that gives us the following folks for the proposed PMC:
Robin Berjon
Michael Nachbaur
Matt Sergeant
Kip Hampton
We (those listed above) need to pick a Chair. Robin nominated me
already; other nominations?
-kip
Howdy Axers,
For those who may not already know, I'll be giving an 3 hour in-depth
tutorial on AxKit at this year's ApacheCon US.
http://apachecon.com/2004/US/index.html
If you haven't ever been to ApacheCon, I simply can't recommend it
highly enough. The conference is focused (all Apache, all t
+1
Matt Sergeant wrote:
I need a few +1s to put up a download for AxKit2.
Voters are:
kip, darobin, barries, jwalt, mach, nachbaur
Matt.
.
Matt Sergeant wrote:
We're in a good stable position now. We have a test suite. We've got
some nice apps shipping with it. I think it's time for a 1.1 release.
+1 here
(committers only voting please).
+1
-kip
55 matches
Mail list logo
