On Tue, Sep 05, 2006 at 11:41:40AM -0400, Dossy Shiobara wrote: > Of course, the more popular languages weren't implemented with > embeddability (embedibility?) in mind. Tcl is one of the only mature > languages that can be safely embedded in a multi-threaded application.
Well, I'm sure some one of the eleventy dozen Scheme implementations out there would be suitable, although I don't know which one. Oh wait, you said POPULAR languages, nevermind... AOLserver does already have Standard ML and Objective CAML modules, which seem to have attracted roughly zero interest from their respective language communities. > A global lock? There goes scalability and the benefits of embedding > Python. (You'd be better off running it in a separate process ala > FastCGI, AOLserver would gain no performance by embedding it, only What exactly is the downside of FastCGI? Is it not feasible to provide 100% of the AOLserver API within the FastCGI constraints? If so, perhaps it would be easier to add interprocess shared memory to some trendy non-threadsafe language, than it would be to make the language implementation threadsafe. One process per interpreter plus shared memory would definitely work for implementing nsv and ns_cache. I don't know how much of the AOLserver core would need to be changed to cope, though. The above all sounds pretty blue sky of course, but just in case there's someone out there REALLY interested in embedding a single threaded interpreter in AOLserver... > After having said all this, I would like to explore the idea of > Server-side JavaScript (SSJS): > > http://en.wikipedia.org/wiki/Server-side_JavaScript Hm, that's actually fairly interesting. My impression is that the Scheme-heads and similar folk also like JavaScript fairly well, btw. Not having used either one, I'd still guess that XOTcl is probably more USEFUL, but since it has "Tcl" in its name I guess it doesn't count. :) > IMHO, this change could put AOLserver back in the beauty pageant. [shrug] If you want to slingshot AOLserver into much greater popularity, presumably one good trick is to catch the fancy of some up and coming development niche or trend and get them to run with it. Your JavaScript idea seems pretty reasonable as such ideas go, but of course there's huge amounts of random chance involved. A simpler first pass approach, which has substantial value in and of itself, would be to clearly articulate WHY you want to make AOLserver much more popular than it is. And I don't mean just the fact that you like it and it would be cool. No, presumably you think AOLserver is SUPERIOR, and you wish more people appreciate and enjoy that superiority. So, write a convincing case for why AOLserver is technically excellent for particular types of uses. A really good design explication of the core server would probably be a big part of that. Ooh, I know, manage to get some job teaching a one semester university class in advanced server design, and use AOLserver as your code reference case and test-bed. The notes you'd develop for the class would probably be an awesome draft for the above. ;) -- Andrew Piskorski <[EMAIL PROTECTED]> http://www.piskorski.com/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
