n***@sourceforge.net
2000-12-20 06:00:42 UTC
Bug #125388, was updated on 2000-Dec-11 13:08
Here is a current snapshot of the bug.
Project: XPLC
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: nobody
Assigned to : pphaneuf
Summary: Dynamic loader service handler
Details: This is a service handler that would look in a directory to load the appropriate loadable module when a component is requested from it.
Should there be a handler per component directory? Or should a single handler be able to look in multiple directories? Order might be important here, maybe there should be a way to control the order in which directories are looked at (the service manager doesn't define any order to call its handler, so we cannot count on this).
There should be a persistent index (see bug #125387) for each directories, that would keep the mtimes of the shared objects and the components they contain, so that they do not need to be all loaded at every run to know what component they contain.
The stored mtime should be compared against the actual one, and the stored information should be dropped and rediscovered upon if they are different.
An initial implementation wouldn't need the persistent index, it could discover everything a-new at every run, but this wouldn't be acceptable for any sizable application.
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=125388&group_id=1814
Here is a current snapshot of the bug.
Project: XPLC
Category: None
Status: Open
Resolution: None
Bug Group: None
Priority: 5
Submitted by: nobody
Assigned to : pphaneuf
Summary: Dynamic loader service handler
Details: This is a service handler that would look in a directory to load the appropriate loadable module when a component is requested from it.
Should there be a handler per component directory? Or should a single handler be able to look in multiple directories? Order might be important here, maybe there should be a way to control the order in which directories are looked at (the service manager doesn't define any order to call its handler, so we cannot count on this).
There should be a persistent index (see bug #125387) for each directories, that would keep the mtimes of the shared objects and the components they contain, so that they do not need to be all loaded at every run to know what component they contain.
The stored mtime should be compared against the actual one, and the stored information should be dropped and rediscovered upon if they are different.
An initial implementation wouldn't need the persistent index, it could discover everything a-new at every run, but this wouldn't be acceptable for any sizable application.
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=125388&group_id=1814