<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2448.0">
<TITLE>RE: [LCP]Dynamic libraries and plugins</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>> I have a also a question regarding dlopen and friends (and </FONT>
<BR><FONT SIZE=2>> when it would </FONT>
<BR><FONT SIZE=2>> make sense to use them)....</FONT>
<BR><FONT SIZE=2>> Say I have a program which is executed often (maybe even </FONT>
<BR><FONT SIZE=2>> several times a </FONT>
<BR><FONT SIZE=2>> second) with many different options. </FONT>
<BR><FONT SIZE=2>> Due to soooo many options would it make sense to put </FONT>
<BR><FONT SIZE=2>> different parts of </FONT>
<BR><FONT SIZE=2>> the code into seperate shared libs and call dlopen() by hand? </FONT>
</P>
<P><FONT SIZE=2>This may not answer your question directly, but if you call</FONT>
<BR><FONT SIZE=2>your program very often, I'd keep a daemon running, and the</FONT>
<BR><FONT SIZE=2>program itself would merely contact the daemon to tell it</FONT>
<BR><FONT SIZE=2>what to do. This way, there is no init time (just when loading</FONT>
<BR><FONT SIZE=2>the daemon).</FONT>
<BR><FONT SIZE=2>However, depending on what you do, it might be too much in</FONT>
<BR><FONT SIZE=2>memory (to keep the daemon in-core at all times). As usual,</FONT>
<BR><FONT SIZE=2>YMMV, each situation may need a different setup.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Vincent Penquerc'h </FONT>
</P>
</BODY>
</HTML>