[EXTENSION] Sockets (2.0.0) - Page 2

sskillz · **Author**

you work is much appreciated.
Where is the source for version 2?

If that is the source for latest version I found a lot of errors in the code.
Should I list them?

l0gen · 02-24-2008 , 11:38 Re: [EXTENSION] Sockets (2.0.0)

Great!

Any news regarding the linux version?

lamdacore · 02-25-2008 , 06:02 Re: [EXTENSION] Sockets (2.0.0)

Quote:

Originally Posted by l0gen

Great!

Any news regarding the linux version?

Yeah I want the linux version, too >_<
I want to use the IRC Relay, but without a linux version of this extension it not possible. I hope this will be available soon.

recon0 · 02-26-2008 , 19:34 Re: [EXTENSION] Sockets (2.0.0)

Quote:

Originally Posted by lamdacore

Yeah I want the linux version, too >_<
I want to use the IRC Relay, but without a linux version of this extension it not possible. I hope this will be available soon.

I'm gonna be getting a server soon... And it's going to run on Linux... Everyone wants the Linux version...

sskillz · 05-06-2007 , 01:21 Re: [EXTENSION] Sockets

I have a plugin waiting just for this ^_^
good work!

Olly · 05-16-2007 , 05:21 Re: [EXTENSION] Sockets

New update, see first post

1.0.2.0

Fixed lots of null pointer crashes ><
Fixed the native name in the include for SocketClose
Fixed functag
Compiled for linux

Olly · 05-06-2007 , 21:29 Re: [EXTENSION] Sockets

Major update, see First Post

sskillz · 05-09-2007 , 13:58 Re: [EXTENSION] Sockets

Good job!
Looks promising, I'll try as soon as my srcds will stop downloading

Just one thing I think is missing is this:

Code:

/**
 * Defines the callback function when a the specified socket closes
 *
 * @param    socket                The id (handle) of the socket to set the callback for.
 * @param    function            The function to use as callback.
 */
native SetSocketCloseCallback(socket, function);

And btw, now if the socket is not connected or gets disconnected, is the handle changes to undefined ? or not > 0 ?

sslice · 05-09-2007 , 16:20 Re: [EXTENSION] Sockets

Very nice.

I would like to see the connect function to be non-blocking with a callback for it though.. for it to be truly non-blocking. Also, like sskillz said, a callback for disconnection should exist, unless the error callback was meant to cover that.

Note: Should the Function: tag be used?

Edit: A good reference would be the asyncore module in Python.

BAILOPAN · 05-09-2007 , 18:03 Re: [EXTENSION] Sockets

o_O yes definitely use the function tag, or even better, use functag.