time@ice.com (Tim Endres) writes: >jar@hopf.dnai.com writes: >> Can anyone shed any more light on this? Most importantly, >> can anyone predict whether a MacPERL-interpreter-plug-in >> is feasible? > >The new plugin technology is little different than all other >plugin stuff on the Mac. It is exciting for WebSTAR in that >it will allow things programmed as CGI's to run "within" the >WebSTAR environment. > >Htpl will be ported to be a WebSTAR plugin, with the most >significant gain being that documents will be convered >directly, as opposed to requiring a cgi interface. > >However, there are serious constraints for plugins, especially >a requirement that they use WebSTAR memory allocation routines >and the like. Thus, I seriously doubt MacPerl will "plugin". >An OSA Perl might be different, however.... I mostly agree. However, it might well be possible to recast the current MacHTTP Perl glue as a plugin, thereby eliminating one of the two AppleEvent exchanges. But as this doesn't eliminate the non-multithreading nature of MacPerl, this is not high on my priorities list (the source code to the CGI clue is available; anyone else is welcome to give it a try). Matthias ----- Matthias Neeracher <neeri@iis.ee.ethz.ch> http://err.ethz.ch/members/neeri.html "One fine day in my odd past..." -- Pixies, _Planet of Sound_