Unsigno Posted August 23, 2017 Report Posted August 23, 2017 I know NodeJs works in a single thread , but the modules work with request that use sessions , then i have the doubt . I need to handle only one offer per account at a time ? Or can I make all the calls to .createOffer I need ? I tested calling the method many times and works, but is it "secure" ? Quote
Dr. McKay Posted August 23, 2017 Report Posted August 23, 2017 The createOffer method doesn't do anything on the network. It just creates a new object in memory, which you can add items to and set properties on. Nothing of value actually happens until you call offer.send(). So that means you can call createOffer as many times as you want. You could call it a million times in a second if you wanted and nothing would break. Of course, sending offers that frequently isn't gonna work. Quote
Unsigno Posted August 23, 2017 Author Report Posted August 23, 2017 Thanks for your fast answer . Sorry i missed the detail , and i mean creating + send ( i have a method that create and send i a row ) . Some concurrency handles for send offers ?? Or what limitation are you mention ?? Quote
Dr. McKay Posted August 23, 2017 Report Posted August 23, 2017 There's no concurrency concern with sending offers, but if you send offers too frequently (or you send too many offers) then Steam will start limiting you. You're limited to 30 total active outgoing offers, and 5 active outgoing offers to the same recipient. There are also request rate-limits. Unsigno 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.