I propose to provide

        flx_web

as the webserver. This is a version of the webserver which has all the required
plugins preloaded and all libraries linked statically. This means plain

        /path-to-bin/flx_web

should "just work" without any environment variables. Note that in the future
a mapping scheme may be used to map filenames to plugins and this
being dynamic would still try run time loading of plugins.

The old "webserver" name was too generic.  Any comments?
flx_http might be better...

My current convention is to call all executables "flx_something".
This would allow deleting them all from /usr/local/bin with a single
wildcard eg on Unix

        rm /usr/local/bin/flx*


The same should apply to libraries, however it doesn't and that's
a bit more work. Felix doesn't currently distinguish load time
libraries such as "libflx_dynamic.so" from plugins (which don't
start with "lib"). Dynamic linkage conventions need to be sorted out.

--
john skaller
skal...@users.sourceforge.net
http://felix-lang.org




------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to