[Zenith77]

I'd think it be pretty cool and useful to have a multi-threaded sockets module like the SQLx module. That's all.

[Twilight Suzuka]

Hey! Thi...this was my idea...

[Greenberet]

...
boys are always faster then girls
even in posting ideas

[Twilight Suzuka]

Originally Posted by Greenberet ... boys are always faster then girls even in posting ideas

Greenberet: I started coding the module long before this was posted. Hell, its probably a joke post, cause it uses my naming convention for modules -> *X

[BAILOPAN]

This would be an interesting project. Sockets work differently from SQLX though and the same model would not directly apply. You'd have to create the socket in the thread, then pump received/sent data to and from the plugin to the thread. That is different from SQLX, which does this atomically for one connection, rather than keeping the connection open and letting the information flow bidirectionally.

[Hawk552]

Originally Posted by BAILOPAN This would be an interesting project. Sockets work differently from SQLX though and the same model would not directly apply. You'd have to create the socket in the thread, then pump received/sent data to and from the plugin to the thread. That is different from SQLX, which does this atomically for one connection, rather than keeping the connection open and letting the information flow bidirectionally.

If you actually do this, could you also add socket server capabilities? You know, like socket_listen and the other stuff that goes along with it. I know you'd probably do it anyway, but just making sure.

[Zenith77]

Originally Posted by Twilight Suzuka Greenberet: I started coding the module long before this was posted. Hell, its probably a joke post, cause it uses my naming convention for modules -> *X

And what do you have to show for it :p.

[Twilight Suzuka]

L...lots!