If you are already making this an object (as opposed to a ds_map), I think it would be a good idea to manage the resources in that object as well; That is, create the buffers/sockets/dses in the Create event, and destroy them in the Destroy event. That way you only need to remember to destroy the object (which you have to do anyway). Only drawback I can think of: The destroy event might not fire on room change, but that's a known issue that affects all kinds of objects. Since it's not persistent, room_goto_fix would take care of it properly. On that count, as it is now changing rooms when a HttpClient exists would leak resources...