<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7652.24">
<TITLE>C Compiler requirement</TITLE>
</HEAD>
<BODY >
<DIV>
<!-- Converted from text/rtf format -->
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">So as I understand it, when Varnish runs, it reads in the VCL script (basically the configuration file that I have written) and generates C source from that code, that is then compiled into a shared object to be called by the accelerator. Is there any way Varnish can compile that beforehand, and then have that Shared Object used on the next launch instead of having it rebuilt again? I'm still going around with having a C compiler on Production boxes, and am waiting for a decision from security, but I was wondering about this. Once configured we're not going to change the VCL ever, so if we could have it built once, and then use that, we wouldn't need a C complier on the Prod box. I may be way off, but just an idea I wanted to discuss, as it would make using Varnish easier for enterprises that don't understand Varnish's philosophy.</FONT></P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">Thanks</FONT>
</P>
<P><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">P</FONT>
</P>
</DIV>
<DIV> </DIV>
<DIV> <SPAN STYLE="FONT-SIZE: 11pt; COLOR: black; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT SIZE="1">If you are not the intended recipient of this message (including attachments), or if you have received this message in error, immediately notify us and delete it and any attachments.<SPAN STYLE="mso-spacerun: yes"> </SPAN>If you no longer wish to receive e-mail from Edward Jones, please send this request to messages@edwardjones.com.<SPAN STYLE="mso-spacerun: yes"> </SPAN>You must include the e-mail address that you wish not to receive e-mail communications. <SPAN STYLE="FONT-SIZE: 8pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"><FONT SIZE="1">For important</FONT> <FONT SIZE="1">additional information related to this e-mail, visit </FONT><A HREF="http://www.edwardjones.com/US_email_disclosure"><FONT SIZE="1">www.edwardjones.com/US_email_disclosure</FONT></A></SPAN></FONT></SPAN></DIV>
<DIV><SPAN STYLE="FONT-SIZE: 11pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN> </DIV>
<DIV><SPAN STYLE="FONT-SIZE: 11pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN></DIV>
<DIV><SPAN STYLE="FONT-SIZE: 11pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN> </DIV>
<DIV><SPAN STYLE="FONT-SIZE: 11pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"></SPAN></DIV></BODY></HTML>