Keep up the good work (y)
Torque - Exploit Protection Proxy for vSRO
12/30/2014 19:27
raulxxxx#31
01/02/2015 13:47
MR ! HЄRO#32
amazing one
01/10/2015 21:45
ILowe#33
Torque good.
very successful business
very successful business
01/12/2015 19:00
Kadhras_TR#34
Reply me when yo're availible. magicanoo
01/17/2015 23:49
magicanoo#35
UP!
Added one more feature (CTF level restriction).
[Only registered and activated users can see links. Click Here To Register...]
Added one more feature (CTF level restriction).
[Only registered and activated users can see links. Click Here To Register...]
01/18/2015 07:45
Tustin1337#36
I'm not surprised you implemented this feature, you have something special in you, keep impressing people, and you'll continue to climb. ;)Quote:
UP!
Added one more feature (CTF level restriction).
[Only registered and activated users can see links. Click Here To Register...]
01/26/2015 22:32
maxxxtoor#37
Nice one, stability is most important for all of the servers.
01/30/2015 22:21
Elyos Online#38
nice
02/04/2015 04:51
Wismo#39
Best Guy, best Service!
02/04/2015 06:47
awful1337#40
awesome work.
02/23/2015 04:22
Mr Z!dane#41
Good job
02/27/2015 19:39
ümitalp#42
PLEASE FIX PC LIMIT FROM PIONEER SRO!
03/06/2015 01:21
Qinshin#43
silkroad protection is not new for me but the ass kicking feature of this Toque is the capability of handling and processing multiple connection at a time, ASYNC. Just like silkroad's gateway, agent & download modules it is using the same method of handling and processing multiple connections, ASYNC... With this tool I can imagine in the near future or maybe this year, we can use a latest silkroad/R client to connect on our vsro/csror servers... :D
My message to the creator of Toque, keep it up clean and simple!
My message to the creator of Toque, keep it up clean and simple!
03/29/2015 10:54
magicanoo#44
UP
Added a new feature (disabling res skills in the CTF to prevent abusing).
Added a new feature (disabling res skills in the CTF to prevent abusing).
03/29/2015 22:47
asdqaz#45
so, first of all nice features ya have here :D but please stop lying to ppl :(
here's a socket comparison: [Only registered and activated users can see links. Click Here To Register...]
as you can clearly see:
DetGuard (or at least the source i've found and based my own proxy upon) used Pure Non-blocking sockets - Calls on non-blocking sockets return immediately, even if they cannot complete their task immediately. Although this allows the program to do other things while the network operations finish, it requires that the program repeatedly poll to find out when each request has finished.
Torque uses Asynchronous sockets - These are non-blocking sockets, except that you don’t have to poll: the stack sends the program a special window message whenever something "interesting" happens. (and it's way easier to code :D)
so it's a lie that ur program performs better than others based on the fact that it's async ... if it does perform better, it's simply due to the way you coded it :D not due to the nature of socket types used :p and even a blocking i/o can perform ok, if it's threaded properly :) that's all, good luck :D
here's a socket comparison: [Only registered and activated users can see links. Click Here To Register...]
as you can clearly see:
DetGuard (or at least the source i've found and based my own proxy upon) used Pure Non-blocking sockets - Calls on non-blocking sockets return immediately, even if they cannot complete their task immediately. Although this allows the program to do other things while the network operations finish, it requires that the program repeatedly poll to find out when each request has finished.
Torque uses Asynchronous sockets - These are non-blocking sockets, except that you don’t have to poll: the stack sends the program a special window message whenever something "interesting" happens. (and it's way easier to code :D)
so it's a lie that ur program performs better than others based on the fact that it's async ... if it does perform better, it's simply due to the way you coded it :D not due to the nature of socket types used :p and even a blocking i/o can perform ok, if it's threaded properly :) that's all, good luck :D