[friagram]

I haven't noticed any problems with socket on my servers, as far as handles being open.

[Mathias.]

After a while it failed when creating allot of connection, it failed to inialise new socket, I am unable to reuse the old one when connection close and yes I close my handle and there is no memory leak.

[darkid]

Originally Posted by WildCard65 You trying to do http stuff? If so, try steamworks.

Steamworks cannot do PUT or DELETE requests, two things I would rather like. Does Socket support both of these?

[asherkin]

Originally Posted by darkid Does Socket support both of these?

Socket doesn't "support" any HTTP requests, it's a low level socket library.

[darkid]

Originally Posted by asherkin Socket doesn't "support" any HTTP requests, it's a low level socket library.

I don't have the right terminology, but I've seen examples of people using sockets to do HTTP requests, and was wondering how extensive the plugin is.

[Mathias.]

Originally Posted by darkid I don't have the right terminology, but I've seen examples of people using sockets to do HTTP requests, and was wondering how extensive the plugin is.

It because you have to create the protocol (not that http will be hard to do), sockets are low level networking, you can follow ftp/html or pretty much any internet protocol and communicate with it. I will recommend you steamwork, from what we told me, it a wrapper of steamwork API (valve api) and offer a http protocol which is super useful for web APIs. I used socket for a long time and had a couple of issues which one of them is the host limit in char and source code is down so don't expect any updates or maintenance. Apparently there is a new official release of socket for 1.7/1.8 that will be release sooner or later (and I can't wait for it)

[darkid]

Steamworks does not support PUT nor DELETE requests, as I said initially. Limits on numbers of sockets is not a problem, unless that limit takes effect at below around 16 sockets.

[KyleS]

Originally Posted by darkid Steamworks does not support PUT nor DELETE requests, as I said initially. Limits on numbers of sockets is not a problem, unless that limit takes effect at below around 16 sockets.

There have always been stability issues with Sockets. Are you sure you need PUT and DELETE? Data is usually POST.

[darkid]

http://wiki.apache.org/couchdb/HTTP_Document_API#PUT

[asherkin]

Originally Posted by darkid http://wiki.apache.org/couchdb/HTTP_Document_API#PUT

And as you can see it supports POST as an alternative (as a huge number of HTTP clients / proxies don't support PUT or DELETE requests).