On 04/21/2010 11:52 AM, Nicolas Cannasse wrote:
There is no step-debugger but Neko bytecodes contains line/file infos
for exceptions stack traces.
Ok, that is quite helpfull and if the generating language, provide rich
error handling, it may not be that necessary.
2. mod_neko (and tora) seems not to be able to read some kind of
apache options (NekoOption ?) am I missing something, or is this
planed in the (near) future ?
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.
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.
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.
Sorry for the strange questions, but I have tried to collect as much
info as possible, but I still need bits and peaces to understand all the
details.
/BL
--
Neko : One VM to run them all
(http://nekovm.org)
