grahamd@otc.otca.oz.au (Graham Dumpleton) (03/21/90)
This mail is mainly addressed to whoever at CMU looks after this aspect of Andrew, however it may be of general interest. For a number of projects we carry out here, ADEW applications have been created to interface into various bits of hardware. Now when someone creates one of these they generally mail it around to everyone and say something like "Hey guys get a load of this" with the idea of everyone trying it and see what they think. Well we have come up with one problem with this. Most of those actively using Andrew here will often sit inside messages all day, now because all the index files are only checked once; when the program is run, if someone sends around mail which references a new object messages will not find it as it only bothers to check its in memory tables for what objects are available. This means that messages must be exited and rerun to get the new object. Is there any problems with having the code for finding and linking in new objects reread any index files which have changed since it last read them, in the event of an object not being found. Would someone at CMU like to comment. Graham Dumpleton (grahamd@otc.otca.oz.au)
tpn+@ANDREW.CMU.EDU (Tom Neuendorffer) (03/22/90)
I just looked over the class code, and , baring unforeseen problems, I expect to get a patch out with the next set of patches that will have class dynamically check for new objects in the classpath if an unknown object is requested. This won't deal with the harder problem of bringing in a new version of an existing object, but it should fix the problem you described. Tom Neuendorffer Manager ATK group ITC / CMU
wjh+@ANDREW.CMU.EDU (Fred Hansen) (03/23/90)
Excerpts from internet.info-andrew: 21-Mar-90 Index files for .do objects. Graham Dumpleton@otc.otc (1166) > Now when someone > creates one of these they generally mail it around to everyone and say > something like "Hey guys get a load of this" with the idea of everyone > trying it and see what they think. Well we have come up with one problem > with this. > Most of those actively using Andrew here will often sit inside messages > all day, now because all the index files are only checked once; The problem is you are using C code which requires additions to the files accessible via the CLASSPATH. This is a big problem if you want to mail you insets to anywhere offsite. Try writing the code for the inset in Ness. Then you can mail the inset anywhere and it will still work. See .../andrew/doc/atk/ness/* If there are problems with using Ness for your tasks, I would be delighted to hear about them so they can be fixed in future patches or releases. Fred Hansen