Every modern application you run on any machine will generally multi-threaded. That's how applications can run something in the background and still allow user input (e.g. allowing you to click the stop button in Abrosia even though it's currently refreshing a shop page).
Your point about keep-alives is true, but what aspect of multi-threading aids that scenario? Having multiple threads doesn't get around the inability to keep a connection open between requests
I don't really see what you're getting out - you're a bit mistaken here:
- Every application is threaded.
- Nothing stops you sending multiple buy requests in one stock with one thread (this is generally why we use asynchronous requests for HTTP)
- Assuming you mean using threads to send requests, you still won't "avoid" any lag on neopets servers because that's out of any application's control
Using multi-threading as a way of using multiple accounts to monitor shop restocks or buy on side shell accounts can be beneficial, but you're all way off of the mark with your reasoning behind why.
It's important to remember that just applying the word 'THREADING' or 'MULTI-THREADED' to an application is just a buzzword that people regard as a synonym for 'fast' or 'efficient' - but that isn't the case - you have to actually know what you're doing and have a decent understanding of thread management for it to offer any kind of improvement.
It's also a pretty quick and easy way to make your application monstrously complex and difficult to support.
A typical program would function like this:
Send SYN to Neo. Wait for SYN, ACK to come back. Send ACK. Now, send HTTP Request to view page. Parse response for item you want. If matched, send SYN to Neo. Wait for SYN, ACK to come back. Send ACK. Now, send POST to buy item. Multi-threading, while not eliminating this inefficiency, minimizes its effect because you'll be sending X amount of parallel requests and POSTs...The more latency involved, the more jitter can effect you. Multi-threading basically provides for the possibility that one of the X threads will be faster than an average single-thread which is huge in Attic where there's only quantity-1 of a great item.
As I'm sure you've noticed, Neo's environment is typically shit. You can make a request, sit for 30 secs waiting for a response, but then re-click your object and get an instant response. There's a fair chance that 1 in X threads will have a good response which again, defeats a random person subject to Neo's crap.