> -----Original Message----- > From: John P. Dodge [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 31. August 2005 15:52 > To: users@httpd.apache.org > Subject: RE: [EMAIL PROTECTED] Compilinf mods_ssl Shared/static > > > On Wed, 31 Aug 2005, Boyle Owen wrote: > > > > > > > Is there a consensus on compiling mod_ssl as shared or static? > > > > It depends on your application which is the more > appropriate. The two possibilities are not provided just to > add a bit of spice to life, they're there because in some > situations it makes more sense to compile-in a module > statically while in others it's better to load it at runtime. > > > > Think about what each entails and the pros and cons of each > approach and then consider your case and decide which is more > appropriate. > > > > Rgds, > > Owen Boyle > > Disclaimer: Any disclaimer attached to this message may be ignored. > > > Thanks Owen, > > The reason I am asking is that I have always compiled mod_ssl > static and I > am now getting feedback from a customer who indicates that > the problems he > is having related to SSLVerifyClient renegotiation are due to > mod_ssl not > being compiled static. He has a static compiled mod_ssl and > indicates that > this operation works fine but in the shared mod_ssl is does not.
There should be no functional difference between a compiled-in and shared object. If there appears to be a difference, it might be related to different environments when the two versions were compiled. The point I was making was that it was more to do with your application. For example, if you run several instances of apache on several servers, and if some are with SSL and others not, it would make sense to load the module only when needed. However, if you were embedding apache in a server which is difficult to access, you might compile in so you have only a single binary to worry about. My gut feeling is that a static compile is a bit more robust since once it's working it will tend to stay working until you mess with it. Rgds, Owen Boyle Disclaimer: Any disclaimer attached to this message may be ignored. > > Somehow I can't see how this operational issue is related. > > Thanks again... > > ---------------------------------------- > "Mon aéroglisseur est plein d'anguilles" > John P. Dodge > Boeing Shared Services > > > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP > Server Project. > See <URL:http://httpd.apache.org/userslist.html> for more info. > To unsubscribe, e-mail: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Diese E-mail ist eine private und persönliche Kommunikation. Sie hat keinen Bezug zur Börsen- bzw. Geschäftstätigkeit der SWX Gruppe. This e-mail is of a private and personal nature. It is not related to the exchange or business activities of the SWX Group. Le présent e-mail est un message privé et personnel, sans rapport avec l'activité boursière du Groupe SWX. This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
