Feature Requests item #983455, was opened at 2004-07-01 16:13
Message generated for change (Comment added) made by mlkersten
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=983455&group_id=56967
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Priority: 5
Private: No
Submitted By: Peter Boncz (boncz)
Assigned to: Nobody/Anonymous (nobody)
Summary: init script should be part of logical module load
Initial Comment:
currently the MIL module loading is split into two
categories:
- physical load (like dll loading/dropping)
- logical load (adding commands + types to fcn tables)
the MIL script initialization is now done only when a
module was not loaded before (physical load)
however, it should be done always (logical load).
now, global variables, and procs introduced by a module
are not seen if a second client loads a module.
----------------------------------------------------------------------
>Comment By: Martin Kersten (mlkersten)
Date: 2007-11-10 11:37
Message:
Logged In: YES
user_id=490798
Originator: NO
It relates to M4, which is depricated.
----------------------------------------------------------------------
Comment By: Fabian (mr-meltdown)
Date: 2006-11-22 22:33
Message:
Logged In: YES
user_id=963970
Originator: NO
isn't this more or less implemented right now?
----------------------------------------------------------------------
Comment By: Niels Nes (nielsnes)
Date: 2004-09-12 15:04
Message:
Logged In: YES
user_id=43556
;-( I want vi for sf bug tracker and all other web forms)
load the mil part (this is needed to get depending
modules loaded)
during the mil load the dll/so is loaded,
using a module
statement.
As long as a module is loaded early (say before mapi) there
are no problems.
Problem is 'mapi 1' loads module en 'mapi 2' also loads module
both start with the load but one stops as the load (dll/mil)
is allready
done.
Its difficult detecting the difference between a (second)
mil load for a server/client case (ie module allready loaded
by server) and a client/client case is difficult.
It should check if the module is loaded by one of his
parents or not!
Conclusion is not for this release, work around is also way
to simple and
should be advocated as the only use of dynamic modules.
Solution is server allway loads modules before loading the mapi.
I think the best solution for the future is to disable
module loading
for clients other then admin and stop loading after mapi is
loaded!
(moved to feature requests)
----------------------------------------------------------------------
Comment By: Niels Nes (nielsnes)
Date: 2004-09-12 15:00
Message:
Logged In: YES
user_id=43556
The module loading is indeed split in 2 parts
physical and logical loading
For any new module (ie combination of dll and mil part)
we go through 2 steps
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482471&aid=983455&group_id=56967
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
