nobody
2001-02-27 22:50:55 UTC
Bugs #225388, was updated on 2000-12-11 13:08
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=101814&aid=225388&group_id=1814
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous
Assigned to: Pierre Phaneuf
Summary: Dynamic loader service handler
Initial Comment:
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.
----------------------------------------------------------------------
Comment By: Pierre Phaneuf
Date: 2001-02-27 14:50
Message:
Logged In: YES
user_id=5633
I don't have enough time at the moment to work on this,
marking as unassigned to indicate that the task is up for
grabs.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=101814&aid=225388&group_id=1814
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=101814&aid=225388&group_id=1814
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous
Assigned to: Pierre Phaneuf
Summary: Dynamic loader service handler
Initial Comment:
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.
----------------------------------------------------------------------
Comment By: Pierre Phaneuf
Date: 2001-02-27 14:50
Message:
Logged In: YES
user_id=5633
I don't have enough time at the moment to work on this,
marking as unassigned to indicate that the task is up for
grabs.
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=101814&aid=225388&group_id=1814