Hi Dave,
On Sunday, March 11, 2012 9:13:12 AM UTC-4, Totally Objects wrote:
Hi Lou. And the problem with SocketSet being a 'bit ' old is what? We are still here and listening
David
Totally Objects
Sorry, I didn't mean any offense. I was just wondering if there was any email package that came with or was recommended for Seaside. After taking a quick look around I am still using SocketSet of all my socket work including email in all my server code including Seaside apps.
The last time I corresponded with Matt, he said he didn't think you guys had any plans to update SocketSet to IP6. So far, I don't think I have a need for IP6 but who knows?
I also have some changes to SocketSet that I would love for you guys to add to SocketSet. Mostly I have changed the way timeouts work. Instead of timeout time covering the entire operation and throwing an error if the operation doesn't finish on time, I use the time out to cover the last activity.
This way, one can set a timeout at say 30 seconds regardless of how long the operation would take. If there is no activity for 30 seconds, one can consider the connection dead. As long as there is activity (on a read or a write) within the 30 seconds, everything is fine. I have thrown a megabyte (or more) of data at a socket without having to change the timeout and worry if it will finish within the time allotted. You only have to set the timeout for what ever time of inactivity you want to wait before giving up on the connection.
The code may take some work if you want to remain backward compatible but it is yours if you want it and I willing to help if you like.
Lou