<a href="http://Squeaksource.com">Squeaksource.com</a> should see an increase in performance in the next day! I just removed two layers of indirection (proxy -> proxy -> squeaksource) and re-programmed the IP address of the DNS A record to point directly to the real server per your request.
<br><br>That's my refactoring contribution to the community this week. Hold your applause.<br><br>Regards,<br><br>John<br><br><div><span class="gmail_quote">On 1/31/06, <b class="gmail_sendername">Adrian Lienhard</b> <
<a href="mailto:adi@netstyle.ch">adi@netstyle.ch</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">yes, the new server (not kilana) listens on port 80 and kilana:8888
<br>proxies requests to it. So the time for the change of the DNS record<br>does not matter.<br><br>Thanks,<br>Adrian<br><br>On Jan 31, 2006, at 05:08 , Colin Putney wrote:<br><br>><br>> On Jan 30, 2006, at 10:54 PM, John Pierce wrote:
<br>><br>>> Ah -- never mind my last message. I have the A record pointing to<br>>> <a href="http://69.55.226.151">69.55.226.151</a> right now. Not sure who that is is, but that's what<br>>> was decided before. I will make the change to the IP you suggest
<br>>> below once you confirm the timeline.<br>><br>> That's the proxy I set up when you had problems a few months ago.<br>> If kilana is listening on port 80 now, it's not necessary anymore.<br>><br>> Colin
<br>><br><br><br></blockquote></div><br><br clear="all"><br>-- <br>It's easy to have a complicated idea. It's very very hard to have a simple idea. -- Carver Mead