both have some global .htaccess options, but there is no local
.htaccess support
Will local .htaccess be supported in the future, and how about auth
handling to make it possible to use neko to control file access and
other things.
To be precise, local .htaccess is working but mod_neko configuration is
only available in global httpd.conf. No plans to change that right now.
Auth can be handled directly through HTTP headers, there's no need for
an additional API.
3. I can see that a SQLite, and MySQL db are available, will a
PostgreSQL db be possible or even welcome ? are mod_neko supporting
persistent connections, or will neko vm restart on every request ?
There is already a haXe/Neko PostgreSQL binding available, you can
implement persistent connections with setting main entry point
function (neko.Web.cacheModule haXe API). Or with tora.Share API
which enable memory sharing on the same server.
Hmm, I have been looking into the neko code (1.8.1-5 from debian repo),
and under libs I only found mysql and sqlite, am I looking the wrong place.
Yes, it's not part of the standard distribution, check on google or on
http://lib.haxe.org
To me it looks like haxe are only able to do things the target platform
supports (postgresql in neko f.ex.), and that get some kind of wrapper
definition (I need more details :-)) that tels haxe how to map it to the
target platform.
Yes that's correct. haXe adds typing to more lowlevel neko NDLL apis.
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
