21–30 of 75 posts
This is not an official Google product. So why did it say Google in the title? This should be clarified.
Earlier quoted context omitted.
I believe it means they want to share the code but not support it like an official product launch, but I don't know for sure.
And then withdraw the code and cancel it once it's in wide use, a la MyTracks?
Earlier quoted context omitted.
I believe it means they want to share the code but not support it like an official product launch, but I don't know for sure.
And then withdraw the code and cancel it once it's in wide use, a la MyTracks?
And I allowed myself to do the code quality analysis on the project: https://codebeat.co/projects/github-com-google-seesaw ;)
And I allowed myself to do the code quality analysis on the project: https://codebeat.co/projects/github-com-google-seesaw ;)
That analysis is pretty bad, the code is clean and straightforward, yet that tool reports a bunch of random non-issues.
Cool to see this engine out in open source.
To build a VPN edge you also need cooperative tiered caches with some very counterintuitive cache admission and eviction algorithms, unicast front end with p2p (for vod) or multicast (for live) back end, multi-datacenter event aggregation and correlation, cookieless/db-less sessions, and a few other goodies, some of which you can now even find as Nginx plugins.
Assembling what you need is much easier now with HLS, DASH, etc., than it was in the MMS/RTSP/RTMP days.
As of last couple years, you could almost assemble a viable global VDN with off the shelf open source parts. If the open compute project keeps up its good work, the physical kit gets affordable too.
Earlier quoted context omitted.
I believe it means they want to share the code but not support it like an official product launch, but I don't know for sure.
And then withdraw the code and cancel it once it's in wide use, a la MyTracks?
LVS load-balancing is amazing. You can use a tiny instance to load balance huge amounts of traffic since the instance itself doesn't need to process and pass the traffic. the part that makes it difficult to implement is that the hosts have to be on the same network. I didn't dive too much into the code but it looks like you also assign an additional interface to use as a VIP. I believe you'll need to be in your own n…
Earlier quoted context omitted.
That analysis is pretty bad, the code is clean and straightforward, yet that tool reports a bunch of random non-issues.
Like near-copy pasta: https://codebeat.co/projects/github-com-google-seesaw/report... ?
[1]: https://github.com/google/seesaw/blob/master/common/conn/con... [2]: https://github.com/google/seesaw/blob/master/common/conn/ipc... [3]: https://github.com/google/seesaw/blob/master/common/conn/rpc...