SSL was implemented long time ago for mining already but was removed again due to the increased network lag.
Lags can only create a pool if it spends a lot of time to encrypt/decrypt data, am I correct?
SSL connection is based on same sockets and it takes almost zero time on client side to encrypt/decrypt 1Kb of data.
I'm curious about server load, is it too expensive to use encrypted connections for you?
Google is a fan of SSL on every site, if it needs it or not, and they care vary much about speed of the internet. If there was a speed issue, it may be different. SSL connection adds a tiny delay to the initial connection, and after that it's negligible.
lol. fuck, this "delay" thingy is a total crap. I'm coming out of the heavily used encrypted pipe (being aes-128-ed on a 30$ wrt router;) with no delays whatsoever so why would I fucking care about few more processed BYTES on my end??? and in regard to the pool side - just watch and see and act accordingly.
also it seems sgminer-gm is improving
That is what I am saying, people blow it out of proportion. Initial connection SSL adds ~100ms for the handshake, but then after that it adds ~0.0000000000001ms per request, since encrypting like a 200 byte packet takes virtually no time, and is probably less than the packet size anyway, so essentially it adds 0 latency. Maybe it would matter on a 56K connection. My rejected rate on 3 different rigs is 0.08%, same as without SSL IIRC, and pool shows 0 stale.
Many sites use SSL, including all google sites, and any shopping site, or generally whenever you login to anything. There may be hundreds of kilobytes, or even megabytes to load a page, and everything is still really fast.