Yes, more or less like greedy torrent.
http://www.sb-innovation.de/showthre...e=3#post215450
Printable View
Yes, more or less like greedy torrent.
http://www.sb-innovation.de/showthre...e=3#post215450
You need Microsoft Visual Studio to open the solution file (*.sln file).
The "My Project" folder contains all sort of information about the program you are creating, like author, version, copyright, resources used by the program, settings, a bunch of things that you don't need to care about because Microsoft Visual Studio handles all of that for you.
It's not like we want the program to be complete, use it for learning (after you learn basic VB.NET skills first),
with that example, you learn how to listen on a port (sockets), asynchronous operations(multiple things doing things at the same time :P), dealing with tracker responses (a bit)..etc.
That's up to you, depending on what you want to do with it.
What do you need to fix?
You can start with the problem of it reporting less upload than last time. Example:
Announce 1:
Upload = 2 Gb
Multiply = 5
Reported upload = 10Gb
User changes multiply from 5 to 2 while the torrent it's running.
Announce 2:
Upload = 2.2 Gb
Multiply = 2
Reported upload = 4.4Gb
You can't lose upload on a real client and that may lead to a ban.
There you go, something to start with.
what language is the proxy tool written in ? cause i tried to search for some of the attributes & didn't find any info about it.
Visual Basic .Net
what i don't understand are these attributes
Code:TorrentClientSocket.BeginReceive(TorrentClientBuffer, 0, TorrentClientBuffer.Length, SocketFlags.None, New AsyncCallback(AddressOf OnReceived), TorrentClientSocket)
Code:'Obtain upload amount
Dim UploadedStart As Integer = GetString.IndexOf("&uploaded=") + 10
@The Shutter You should be reading about asynchronous sockets first. Better yet about threading and implicitly about forking. Good programmers always know their toolset. It's not that hard to jump in and understand clear code that others have written in higher level programming languages but when you try to develop something I highly doubt anything good will come out of it without good practice before hand.
And another thing, you mentioned you were a web developer. My suggestion to you is the following: decide on one thing and one thing only and keep working at it. Most good programmers are polyglot, but as it turns out to be good they only focus on one domain. It's good to have written something in let's say Haskell or done scripting in *nix, because trying things out of your comfort zone grows you as a professional, but try sticking with your piece of bread and practice, practice, practice. When you reach a level where using that specific toolset is like breathing and you say to yourself that you still aren't good enough than you've become a good programmer.