Resources are complicated. And, as we saw in Section ![[*]](crossref.png) ,
Beatrix's FileSystemLocator and SocketFactoryLocator
handle all that work for us. So why did we need to know all the detail
in the last section?
,
Beatrix's FileSystemLocator and SocketFactoryLocator
handle all that work for us. So why did we need to know all the detail
in the last section?
Well, if we're happy with those plugins, then we don't. But if either of them fail to find a particular resource then worker creation fails, and that might not be what we want. If disk isn't available then the worker might still want to run, but omit some of its functionality. Or it might delegate that file system work to another netlet. And if it fails to find a 16-port socket factory it might work happily with two 8-port factories.
Accessing the lower levels gives us greater flexibility. The skeleton application does this with its socket factory.
Nik Silver 2002-03-09