On 8-Aug-06, at 4:24 AM, Peter Mueller wrote:
But I have to say that an Apache 2.x frontend proxying to an perl-
written
backend with AxKit 2.x maybe with changed interfaces which means
that I
would have to rewrite my dirty little Applications is of no use for
me.
I even got blamed inside my company for using such a "big" toolkit
because
after the first app was finished a downsizing to emedded systems as
low
end platform was discussed, and Apache+mod_perl+AxKit etc is much to
big for that.
If I have to start from scratch again I think I will have to go the
oposite
way and do everything by hand again and use as few toolkits as
possible
as all the XML libraries and all this stuff blows up your
environment so
you need a big server just to put up a Hello world message.
I'm not quite sure what you're looking for here. The first part of
your message indicates you want an AxKit2 that's a direct port of
AxKit1 [*]. The second part indicates that you want a small
lightweight server that would be nice and easy to embed. I think
AxKit2 satisfies your second need. Running the gallery my AxKit2
install sits using zero CPU consuming 15M of ram (and I think most of
that is taken up by XML::LibXSLT and LibXML). And that would be your
entire setup on an embedded system - no need for Apache/mod_perl.
Matt.
[*] I did investigate this, and even start to hack on it a bit, but I
wanted AxKit2 to be much easier to use and much easier to hack on -
AxKit1 got huge and complicated and ugly, and a port would have taken
all that cruft along with it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
