Wiki content at About Changed by someone at IP 80.131.80.237 :
@@ -8,6 +8,6 @@
Use the sidebar to navigate to particular sections of the wiki. If you wish to
edit a page, just click on the "Edit this page" link at the bottom of the page,
and edit away. The default page format is POD - Plain O
Wiki content at About Changed by someone at IP 80.131.80.237 :
@@ -8,6 +8,6 @@
Use the sidebar to navigate to particular sections of the wiki. If you wish to
edit a page, just click on the "Edit this page" link at the bottom of the page,
and edit away. The default page format is POD - Plain O
Wiki content at About Changed by someone at IP 80.131.80.237 :
@@ -8,6 +8,6 @@
Use the sidebar to navigate to particular sections of the wiki. If you wish to
edit a page, just click on the "Edit this page" link at the bottom of the page,
and edit away. The default page format is POD - Plain O
Wiki content at About Changed by someone at IP 80.131.80.237 :
@@ -8,6 +8,6 @@
Use the sidebar to navigate to particular sections of the wiki. If you wish to
edit a page, just click on the "Edit this page" link at the bottom of the page,
and edit away. The default page format is POD - Plain O
On 6 Apr 2004, at 17:13, Kip Hampton wrote:
I suggest that we take the opportunity that (potentially) becoming a
top-level project provides to take stock, put aside old baggage, and
move AxKit forward with renewed vigor. To that end, I've put together
a first draft proposal for the guidelines an
- There's no easy way to change the pipeline mid-stream with a pull
model
There is code in there now to allow append to the front (from current
position),
and append to the end. The problem comes if you want to add stuff in
the middle :)
But there is ways to do that if you know in advance wher
(A push pipeline, each stage is run independantly, the output pushed
to the next handler).
A pull pipeline looks just like a function call stack, starting at the
outside... which means each stage ask the stage before it for the
representation it wants before getting it, which allows for lots of
sel
Thanks Mike,
I'll take a look this afternoon. The most important thing for me is
Apache2 since all our mp-stuff is running now on mp2.
Maybe I could spend sometime to get it run on Apache2 or at least
identify what has to changed todo so.
Tom
Mike Chamberlain wrote:
On 19 Apr 2004, at 09:29, Mike C
On 19 Apr 2004, at 09:29, Mike Chamberlain wrote:
Yeap,
First off.
* THIS IS NOT AN OFFICIAL RELEASE. **
Do not expect this to work the way the current or future axkit's will
work.
Do not take this code as in indication of what any final product will
look like.
etc etc.
**
Yeap,
First off.
* THIS IS NOT AN OFFICIAL RELEASE. **
Do not expect this to work the way the current or future axkit's will
work.
Do not take this code as in indication of what any final product will
look like.
etc etc.
*
Having said that, any
Hi Mike,
is it somehwo possible to take a look at what you've done on
pipeline/apache2 stuff?
Thx
Tom
Mike Chamberlain wrote:
[1] http://totalcinema.com/axkit/axkitguidelines.xml
+1 from me.
I like the idea of having a Pumpkin, I think the problem we've been
having recently is
no one has been
This is the automated build report from the AxKit smoke tester
not ok 1
tv: after last 'ok/not ok':
Failed Test Stat Wstat Total Fail Failed List of Failed
---
uri/axkit.t11 100.00% 1
2 subtests skip
12 matches
Mail list logo
