| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | MORE SETUP PROBLEMS |
02 Apr 16 13:04, you wrote to me: gr>>> You could do it with Mystic by creating an "in use" semaphore file gr>>> when you execute it, then removing it when execution is done but gr>>> there isn't anything specifically built in for that because Mystic gr>>> does not store any configuration for any doors. ml>> feature request: mystic could have an option in the door execution ml>> commands where you could specify if the door is single user or not... ml>> then mystic would know when a user was in the door and prevent others ml>> from accessing it... it could use a simple prompt line or possibly ml>> even have a custom screen for this notification... NB> Not sure why the extra effort is needed when 99.9% (I honestly don't NB> know of any that are still popular today that DON'T do this) of the NB> single user door games handle that themselves with the INUSE.FLG or NB> something similar. The door game itself will shoot a message to the NB> second user trying to play saying the game is unavailable at the NB> moment, and to try again later. you and others are thinking only of modern doors written in the 90s that do handle this on multinode bbses... there are, however, older doors that have not been updated that do not... some of those doors are or were fairly popular... unless i'm mistaken, daryl has several hundred doors on his system and some of them are quite ancient and do not have this capability... attempting to trap this in a script file is ok but there is still the possibility of two or more nodes still executing the door if they check the inuse flag file at the exact same time... a race condition it is called... i've always wished that bbses had this ability and have it in the list of things to be implemented in my own bbs code if/when i ever get back to it... doing it in the door itself is better than in the script but there's still the race condition aspect to deal with... besides, it is only a feature request... )\/(ark Always Mount a Scratch Monkey ... Famous Last Words: "Wife! These biscuits are tough!" ---* Origin: (1:3634/12.73) SEEN-BY: 203/0 633/267 280 640/384 1384 712/620 848 770/1 @PATH: 3634/12 123/500 140/1 221/0 1 203/0 640/384 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.