charon Posted February 2, 2021 Report Share Posted February 2, 2021 The steam-user instance use tcp or websocket to keep alive to the steam server, it's stateful, not like steamcommunity connection, the http connection is stateless, so we can cache the http cookies, and load cookies as we needed any time, no need to keep a steamcommunity instance. but the steam-user use a alive connection, so we have to always keep a steam-user instance in memory, when there are a lot of steam-user instances, it's hard to manage them, how many steam-user instance show be managed in one node.js process and how to partition a lot of steam-users, it may be a large project. any advice or experience about this ? thank you. Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted February 2, 2021 Report Share Posted February 2, 2021 There's no real limit on how many steam-user instances you can run in one process; your biggest limitations are going to be memory and IP addresses. Quote Link to comment Share on other sites More sharing options...
charon Posted February 2, 2021 Author Report Share Posted February 2, 2021 10 minutes ago, Dr. McKay said: There's no real limit on how many steam-user instances you can run in one process; your biggest limitations are going to be memory and IP addresses. if all the instance are managed in one process, every time reboot the process all steam-user need to login again, it' a big affect! Quote Link to comment Share on other sites More sharing options...
Dr. McKay Posted February 2, 2021 Report Share Posted February 2, 2021 Yes, for that reason you probably want to split up your stuff into multiple processes. Quote Link to comment Share on other sites More sharing options...
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.