Well, Ray put this better in words, hence he seems
have more insight into it. I've been lurking around
this discussion since Michael's post that once again
began a discussion on what methods would be the best.
This is how I figure though after reading this and
some similar threads:
I for one was very fond of java to begin with - that
is when it was fairly new in the webdevelopment world
- but as it never really took off for webuse (probably
because of the loadtime glitch usually connected to
it) I wouldn't want to include it as middleware in a
DynAPI serverTasks the way I would do it.
So sorry, Michael, mind you I'm not stating you're
method is bad (I'm quite impressed actually), but if
we're going to keep serverTasks as compatible as
possible I think we better stay off using java or
anything else (including Flash as someone suggested)
as middleware and try and have as many serverside
scripting platforms covered - at least the major ones
in use - and allow for addition of others as far as
possible.
Once again I'm the stubborn one, eh? ;)
BTW, I'm considering this one of the first step
towards the DynAPI-based DynBuilder. I think someone
stated this would be one of the biggest woe's in its
creation, so I'm working on it though I'm pretty slow
on progressing.
Henrik Våglin [ [EMAIL PROTECTED] ]
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/?.refer=text
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
