On Thursday, Feb 13, 2003, at 01:32 Europe/London, S Woodside wrote:
Whoa, I missed that. Does that mean that I can validate now in AxKit
somehow using RNG?
No, it requires support in XML::LibXML. That shouldn't be *too* hard,
but I don't have time to do it. Not sure whether Christian has or
On Thu, 2003-02-13 at 02:32, S Woodside wrote:
Whoa, I missed that. Does that mean that I can validate now in AxKit
somehow using RNG?
its early days; the relaxng support is not finished
or efficient, according to Daniel, but in the medium term, yes,
it should be possible to validate using RNG
Fair enough; unless you're validating a document that's being managed
as part of a CMS or some other kind of system.
simon
On Thursday, February 13, 2003, at 03:05 AM, Sebastian Rahtz wrote:
b) validating at delivery time seems wrong to me; it should be done
at author time before a document
S Woodside wrote:
On Thursday, February 13, 2003, at 03:05 AM, Sebastian Rahtz wrote:
b) validating at delivery time seems wrong to me; it should be done
at author time before a document is committed for publishing
Fair enough; unless you're validating a document that's being managed as
but
a) we have no mechanism comparable to DOCTYPE for indicating
what schema to use, so its not clear how one would record that
b) validating at delivery time seems wrong to me; it should be done
at author time before a document is committed for publishing
Sure, but those are pretty
On Fri, Feb 07, 2003 at 07:54:04AM +, Matt Sergeant wrote:
The good news is that libxml2 now supports both XSD and RelaxNG.
really? tell me more!
--
Sebastian Rahtz OUCS Information Manager
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
Whoa, I missed that. Does that mean that I can validate now in AxKit
somehow using RNG?
simon
On Friday, February 7, 2003, at 03:04 AM, Sebastian Rahtz wrote:
On Fri, Feb 07, 2003 at 07:54:04AM +, Matt Sergeant wrote:
The good news is that libxml2 now supports both XSD and RelaxNG.
Yes, SQL sucks awfully bad. However it doesn't have to be typed, which does
make things a lot less silly. See http://www.sqlite.org/datatypes.html for
info on how SQLite isn't typed. I'm not completely up to speed on the
relational model, but I see no reason that it would need typing. It
Well, I'm not an expert on RNG by any means, so I won't get into a debate
about which is better. I expect it depends on the task... SOME form of schema
is very necessary however for many applications. When you say below let the
software figure out the way the software figures out IS TO USE A
On Thursday 06 February 2003 02:38 am, Matt Sergeant wrote:
On Wednesday, Feb 5, 2003, at 20:16 Europe/London, Tod Harter wrote:
1) an IDL generator that can take a server class and generate the WSDL
to
describe the corresponding service.
I have in progress a B::SAX (B is the perl backend
On Thu, 6 Feb 2003, Tod Harter wrote:
Where do you find the time?
In the corner next to the battery meter.
--
!-- Matt --
:-get a SMart net/:-
Spam trap - do not mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL
Based on the recent comments on the XSL list and virtually everythign
else I read when I was researching, WXS is /very/ unpopular, basically
because no one can understand the spec. I took the hint and after
skimming it (and it's lng) went with relax NG which is very simple
and
: Re: AxKit for web applications
Sounds to me like his system is basically identical in most respects to
the
one I came up with for a virtual private exchange (sort of an auction
server
type system). We used SOAP::Lite entirely, each XSP taglib was just a
thin
wrapper over a stub API that called
Tom Howe wrote:
The only issues I have with this is that the XPathScript transformations
are not that fast, especially as there are multiple XPathScript
stylesheets applied for each page.
This is *not* at all to feed the XPS vs XSLT thread, but if you have XPSs that
do only transformations (ie
- Original Message -
From: Tom Howe
To: 'Tod Harter' ; 'Pavel Penchev'
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 10:56 AM
Subject: RE: AxKit for web applications
All this talk of beans and Java and I start coming out in a rash :)
I agree to Tod
Message -
From: Robin Berjon
To: Tom Howe
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 12:26 PM
Subject: Re: AxKit for web applications
Tom Howe wrote:
The only issues I have with this is that the XPathScript transformations
are not that fast, especially
On Wed, 5 Feb 2003, Pavel Penchev wrote:
We were using XPathScript - it is a wonderfull tool but in reality
LibXSLT is times faster. This was the main reason we started using XSLT
instead XPS.
I think some STX that was mentionioned as planned for AxKit 1.7 will be
a great solution :)), even
- Original Message -
From: Tom Howe mailto:[EMAIL PROTECTED]
To: 'Tod Harter' mailto:[EMAIL PROTECTED] ; 'Pavel
Penchev' mailto:[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 10:56 AM
Subject: RE: AxKit for web applications
All this talk of beans
which are the very first and the very last AxKit request points.
Pavel
- Original Message -
From: Matt Sergeant
To: Pavel Penchev
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 1:35 PM
Subject: Re: AxKit for web applications
On Wed, 5 Feb 2003, Pavel Penchev wrote
and Tangram sounds interesting - im certainly going to look into
them.
-Original Message-
From: Tod Harter [mailto:[EMAIL PROTECTED]]
Sent: 04 February 2003 22:19
To: Pavel Penchev; Tom Howe
Cc: [EMAIL PROTECTED]
Subject: Re: AxKit for web applications
Sounds to me like his system
On Wednesday 05 February 2003 06:01 am, Pavel Penchev wrote:
There are nice things my I'm more concerned how a piece of code that is
going to be deployed in the app server is described. Again Java but.. as an
example the EJB is described by a interfaces (Local, Remote), the code that
really
On Tuesday, Feb 4, 2003, at 04:13 Europe/London, Kip Hampton wrote:
Given that a Provider has access to everything that is available for
the Language modules *and* gets to control both the content and the
styles that are applied, how does it lack flexibilty, exactly?
Simply because the
Matt Sergeant wrote:
On Tuesday, Feb 4, 2003, at 04:13 Europe/London, Kip Hampton wrote:
Simply because the Providers are read only at the moment, so there's
no direct method for submitting changes back
Explain read only in this context. What changes, back to where?
The provider's default
brian wheeler wrote:
On Tue, 2003-02-04 at 01:29, Kip Hampton wrote:
I personally favor using something like CGI::XMLApplication because the
model fits the way I like to work, but nothing that baroque is required.
Again, as long as it can return an XML document to the Provider when
needed,
Here at Deluxe Media Services we use AxKit at the front end (on our
webservers) and a custom perl application server sitting behind to handle
all our business logic. All database queries, data munging, session
handling etc is handled on the application servers.
Every page requested is based
server as open source ;))
Pavel
- Original Message -
From: Tom Howe
To: Robin Berjon
Cc: brian wheeler ; [EMAIL PROTECTED]
Sent: Tuesday, February 04, 2003 5:30 PM
Subject: Re: AxKit for web applications
Here at Deluxe Media Services we use AxKit at the front end
Fast enough :) Actually its quite peppy for what we're doing, though
it does require a bit more memory, since all filter stages are kept in
memory.
Generally we're bulk generating things that don't change, but for data
lookups and things of that nature, its pretty easy to whip up an xml
On Tuesday, 04. February 2003 20:47, Tom Howe wrote:
Since every page request requires the users session to be pulled from
the database and the sessions can (occassionally) be over a meg its
important that the messaging system is quick and so far we havnt had any
problems. In fact the
.
If you made it this far, well done :)
-Original Message-
From: Jörg Walter [mailto:[EMAIL PROTECTED]]
Sent: 04 February 2003 20:06
To: [EMAIL PROTECTED]
Subject: Re: AxKit for web applications
On Tuesday, 04. February 2003 20:47, Tom Howe wrote:
Since every page request requires
Granted. ANYthing that can execute perl code in the context of a request
object can do WHATEVER you want, the only question is how easy is it and how
reuseable, and how easily can it call on code written by other people that
does useful stuff?
I guess what I'm saying is that XSP has a lot of
done some work in the bean direction.
Are you planning to release the app server as open source ;))
Pavel
- Original Message -
From: Tom Howe
To: Robin Berjon
Cc: brian wheeler ; [EMAIL PROTECTED]
Sent: Tuesday, February 04, 2003 5:30 PM
Subject: Re: AxKit for web
So...
How are people turning information from SQL databases into XML for AxKit?
I'm thinking the best way to do this would be to use a provider. Has
anyone done this yet?
My concept is that a generic provider could take the rows returned by DBI
and parse them into XML.
So a query like: SELECT
On Mon, 3 Feb 2003, David Chaplin-Loebell wrote:
So...
How are people turning information from SQL databases into XML for AxKit?
I'm thinking the best way to do this would be to use a provider. Has
anyone done this yet?
My concept is that a generic provider could take the rows returned by
On Monday, Feb 3, 2003, at 19:09 Europe/London, Kip Hampton wrote:
Matt Sergeant wrote:
It's one way to do it. I personally haven't used the provider method
(see
the Wiki for how I did it), because I feel it lacks flexibility.
Given that a Provider has access to everything that is available
S Woodside wrote:
Question: What's an application framework in the context of this
discussion?
Could be any hunk of code, really; as long as it can return an XML
document to the Provider on demand, it doesn't matter.
I personally favor using something like CGI::XMLApplication because the
35 matches
Mail list logo
