Muddleftpd - Flexible, secure FTP Daemon - Tasks: task #1530, Module Support
You are not allowed to post comments on this tracker with your current authentication level.
task #1530: Module Support
Submitter: | Joerg Jaspert <ganneff> | ||
Submitted: | - | ||
Category: | program | Should Start On: | - |
Should be Finished on: | - | Priority: | 8 |
Status: | None | Privacy: | Public |
Assigned to: | None | Percent Complete: | Any |
Open/Closed: | Open | Effort: | 0.00 |
Wed 13 Nov 2002 12:47:43 PM UTC, comment #2: |
Beau Kuiper <rugger> |
Wed 16 Oct 2002 03:18:56 AM UTC, comment #1:
|
Beau Kuiper <rugger> |
No files currently attached
Depends on the following items: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2002-10-15 | ganneff | Priority | 5 - Normal | None |
Powered by Savane 3.13-f8d8.
Corresponding source code
Secondly, the modules support should be configured so that muddleftpd passes a structure of pointers to common functions (like safe_snprintf, config functions, ect) to the module when it is loaded.
Then, the modules use those pointers to access functions within muddleftpd.
Pros:
1) Can get rid of the -rdynamic switch on gcc, that bloats muddleftpd's executable.
2) Can strip the muddleftpd executable, without killing module functionality.
3) This all means muddleftpd is even more portable.
4) We get to specify only the interface we want modules to access.
Cons:
1) Slower. Function pointers are slower than dynamic linking.
2) More complex.