vardump

1366 ms·

3571.
by vardump 14y ago
No, I don't know anyone who does this. This is just a curiosity for me. No idea if it's worth it. Measure. Build a test case that implements a limited version or emulates this somehow. Test it against some group for a few weeks or months. D
3572.
by vardump 14y ago
Or you could just "virtual host" by initial URL path, like "hxxp://10.0.0.1/host.sample.com/picture.jpg" or "hxxp://10.0.0.1/p2ezQ/picture.jpg".
3573.
by vardump 14y ago
This only moves the logic you need to do in CDN DNS server to somewhere in your web serving stack. You could still implement crude geographical load-balancing by simply looking at client IP address for example at your load balancer/reverse
3574.
by vardump 14y ago
This got me thinking... When TLS, cookies or same origin policy are not a concern, why not resolve resource domains on the server side and output for example <img src="hxxp://10.0.0.1/picture.jpg"> to avoid that extra client side DN
3575.
by vardump 15y ago
Actually, a modern CPU loads a whole L1 cache line at once. Which is usually 64 bytes nowadays.
3576.
by vardump 15y ago
I read this as RPC with code instead of just data. If so, this is exactly what I've been looking for a long time, because traditional RPC roundtrip latency is often high - so high, that you need to create a more complicated API to avoid exc
3577.
by vardump 15y ago
Care to elaborate? Disclaimer: I've written [EW]MF parser + rasterizer from scratch. I don't see how they're not resolution and/or device independent.