>Currently I'm using dynamically loaded .dll's to provide a plugin system
>for my application, only, delphi bloats .dll's quite a bit making each
>one around 100-150k, which is compleatly overkill when the function
>being called is only 5-10 lines long (the functions often create a
>TQuery and connect into a database to perform lookups).
I've done so at an experimental level and found that this is the ideal candidate
for runtime libraries... The experiment involved
1 Application
an arbitrary number of plugin report modules (2 tested)
an arbitrary number of plugin forms (2 tested)
a single backend dll for each application atom (somewhat arbitrary building blocks).
Performance was affected as:
1. A very long load up.
2. Larger memory requirements.
3. Poor crash recovery... such that resource release was poor under crash conditions...
Interactive performance loss was not hugely significant since processing tended to
remain within function blocks with most interblock communication either instructive
or data transfer.
>Has anyone experimented with using other forms of plugin methods?? I've
>thought about looking at using a scripting language, such as MS
>Scripting Host (where can I download that from anyway?) but wasn't sure
>about how I could use that to link back into my database to perform
>calculation lookups.
>Does anyone know how it works?? Can I make certain
>variables/events/objects in my application available to the MS Scripting
>engine or what???
The scripting will likely have poorer performance balanced with better functionality.
Security of scripts may be an issue also. i would be guessing a bunch off callbacks
for custom functions (name and parameters) and similar for variables.
--
Aaron Scott-Boddendijk
Jump Productions
(07) 838-3371 Voice
(07) 838-3372 Fax
---------------------------------------------------------------------------
New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
