From: Mikael K. <mik...@cr...> - 2007-04-03 21:06:54
|
About making Yaws more pluggable I wonder if something like OSGIs Service=20 Registry and so called white-board pattern could be of any use. Now OSGI is Java, but I think the concepts could be useful anaway :-) Actually Erlang/OTP already solves a lot of the basic things in OSGI=20 (lifecycle management and component deployment) I think and adding somethin= g=20 like a Service Registry could make it more easy to build "component" based= =20 apps. =20 The second link actully has an example of registering a servlet into a http= =20 service.=20 http://www.osgi.org/documents/osgi_technology/whiteboard.pdf http://www.knopflerfish.org/osgi_service_tutorial.html http://www.osgi.org/documents/collateral/TechnicalWhitePaper2005osgi-sp-ove= rview.pdf Regards Mikael l=C3=B6rdag 24 februari 2007 01:26 skrev Roberto Saccon: > I have one feature request I would like to bring into this discussion: > making yaws more pluggable. > > Let me give a concrete example for better illustration: > > in yaws conf there should be an option to define a module name for the > yaws_session_server functionality. When somebody now wants to have session > data stored e.g. in mnesia, or tight into some external application, he > just brings in his own implementation of yaws_session_server, defines it = in > yaws.conf and can continue to use the yaws_api for seesion specific stuff > without changing anything in his web app. > > Now I hope this all makes sense. In case there is an easier way to achieve > the same, I would love to get educated ... > > regards |