<div>Thanks Mark.</div>
<div> </div>
<div>In fact, my goal is to reduce the step : client > tracker > mysql > tracker ...</div>
<div>I'd like to be able to have one MogileFS installation, cache docs at the top level, and if required in a few months, to replicate on another location my squid farm (idea is to build a little custom CDN).</div>
<div> </div>
<div>If I add appropriated headers (Expires, Last-Modified..) to the MogileFS client API when it returns content, Squid can cache the result, no ?<br><br> </div>
<div><span class="gmail_quote">2006/6/26, Mark Smith <<a href="mailto:mark@plogs.net">mark@plogs.net</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">> Is it possible to put Squid in front of MogileFS tracker ?<br><br>In front of the storage nodes, yes. Not the tracker - that speaks a
<br>custom non-HTTP protocol.<br><br>But if you're talking about the part that serves the files, sure. You'd<br>have to run both a webdav server (such as mogstored, or lighttpd) as<br>well as your squid cache - just put them on separate ports.
<br><br>Then, you can configure your hosts to set the alternate GET port to send<br>all of the retrievals to your squid cache. For example, if you take a<br>standard storage node, called store1, with mogstored/lighttpd running on
<br>port 7500 (default), you could start squid on port 7600, and then do:<br><br>$ mogadm host modify store1 --getport=7600<br><br>That would modify store1 and change the GET port to 7600. Once that's<br>done, all URLs returned by the tracker will point at :7600 on the
<br>destination machine - but only for GET requests.<br><br>That should do what you want...<br><br><br>--<br>Mark Smith<br><a href="mailto:mark@plogs.net">mark@plogs.net</a><br></blockquote></div><br>