As far as I understood, it would not be the solution for this case.
As the web-interface, is latency dependent, and the caching server would be
just as remote from user, as is the primary server.
So instead of:
A -> C (dc)
will be
A -> B -> C (where B will only increase the latency)
Appropriate solution would be like stated in original message.
Use server C as X-host, whereas server C only have redraw latency, which
may not be too crucial in this exact case.
OnTopic:
Make use of X network transparency, ssh X forwarding, to forward a
browser(luakit perhaps) to from server B to A.
On Fri, Mar 29, 2013 at 12:30 PM, Phil Thompson <p...@yarwell.demon.co.uk>wrote:
> On Thu, 2013-03-28 at 13:39 +0000, Mark Rogers wrote:
> > However, I already have a headless (ie no keyboard/mouse/monitor, and
> > currently no X) server on-site ("C") that I can reach via SSH. In
> > principle there's no reason why I can't use this instead of installing
> > something new (B). So my question is: what do I need to do on C to
> > allow me to access it via remote desktop and run a browser?
> >
>
> My first thought was a proxy / cache server with clients pointing their
> browsers at C and C updating from A.
>
> But that's as far as I got :-)
>
>
> Phil
>
>
> _______________________________________________
> Peterboro mailing list
> Peterboro@mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/peterboro
>
--
Regards,
David Aizenberg
Peterborough, United Kingdom
+44 7831 649 207
www.linkedin.com/in/pixelshuck <http://about.me/PixelShuck>
_______________________________________________
Peterboro mailing list
Peterboro@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/peterboro
