| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | An interesting question |
Hi Neil! :-) NH> What I NH> envision is some way for a module to be able to tell a controller: NH> 1. that it exists. NH> 2. what it does. This would be a string supplied by the NH> module itself (such as: "What is the meaning of life"). NH> 3. what function would have to be called in order for the NH> module to spring to life. NH> Does anybody have an idea how I could implement such a beast? Sounds like CORBA with that controller of yours being the object broker. Probably overkill, though. Basically you need a daemon of some sort running. It needs to provide just two functions: one that modules can call with the information you listed above and another that interested parties can call to get a list of known modules, their description, and the function to call. That leaves the question on how to locate and call the module once it's name is known. Depends on what the modules really are, they could be standalone programs or loadable library modules or ... ;) Ciao Pascal --- Msged/LNX 6.1.1* Origin: Even the boldest zebra fears the hungry lion. (1:153/401.2) SEEN-BY: 633/267 270 @PATH: 153/401 307 140/1 106/2000 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™.