Re: [felix] web, wiki, libs

On 31/05/2012, at 6:00 AM, Michael Maul wrote:

> That is there to support web_server.flx as it is small it could easily be absorbed in to web_server.flx .
web-server.flx provides a way for all those fancy standards to interact with the outside world.
Thematically I think web_server fits in web, however perhaps we might create a say  servers folder under
lib. Taking that a step further perhaps even develop an abstract interface for "servers", so you can
interact with different types of servers through a consistent and familiar interface.

That's probably hard, since by nature different servers do different things :)

I'm also looking at the naming "lack-of-"policy:

~/felix>ls build/release/lib/rtl/*.dylib
build/release/lib/rtl/libdemux_dynamic.dylib		build/release/lib/rtl/libflx_gc_dynamic.dylib
build/release/lib/rtl/libfaio_dynamic.dylib		build/release/lib/rtl/libflx_pthread_dynamic.dylib
build/release/lib/rtl/libflx_async_dynamic.dylib	build/release/lib/rtl/libflx_re2_dynamic.dylib
build/release/lib/rtl/libflx_dynamic.dylib		build/release/lib/rtl/libjudy_dynamic.dylib
build/release/lib/rtl/libflx_exceptions_dynamic.dylib	build/release/lib/rtl/libtre_dynamic.dylib

since it seems all this has to go in /usr/lib etc to avoid always setting LD_LIBRARY_PATH
which is a PITA.

Downside of current plugin technology .. plugin code cannot be statically linked,
if only because of gratuitous name clashes such as "setup" in the web plugins,
but also because of the "_init_" procedure used to initialise the global data
object (thread_frame).

Of course this can be somehow fiddled with but it's all a bit painful.