[vwnc] Subsystem framework needs a "postrequisites" method

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] Subsystem framework needs a "postrequisites" method

Terry Raymond

The subsystem framework appears to have been designed to be

pluggable. However, it falls short in one area. If one needs to insure that

a subsystem activates “before” an existing subsystem then the

#prerequisites method of the existing subsystem must be modified to

make it happen. If there were a #postrequisites method then modification

of the existing #prerequisites method would not be required.

 

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Subsystem framework needs a "postrequisites" method

Terry Raymond

After I sent this message I found the ‘prerequisites’ pragma. That does it.

 

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================


From: Terry Raymond [mailto:[hidden email]]
Sent: Friday, March 06, 2009 4:28 PM
To: VWNC ([hidden email])
Subject: Subsystem framework needs a "postrequisites" method

 

The subsystem framework appears to have been designed to be

pluggable. However, it falls short in one area. If one needs to insure that

a subsystem activates “before” an existing subsystem then the

#prerequisites method of the existing subsystem must be modified to

make it happen. If there were a #postrequisites method then modification

of the existing #prerequisites method would not be required.

 

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] Subsystem framework needs a "postrequisites" method

thomas.hawker
In reply to this post by Terry Raymond

Terry,

 

You don’t need them.

 

You can add methods to an existing subsystem that has the <prerequisites> tag.  That method answers the subsystems that must be run first.  You can do this to existing subsystems providing the one you want to change isn’t already active when you load such an extension method.  I’ve been doing this since I converted my daemon startup logic to use subsystems in VW7.4.1 – a couple of years ago.

 

Cheers!

 

Tom Hawker

Senior Framework Developer

Home

+1 (408) 274-4128

The Environment:

We take it personally

Office

+1 (408) 576-6591

Mobile

+1 (408) 835-3643

 


From: [hidden email] [mailto:[hidden email]] On Behalf Of Terry Raymond
Sent: Friday, March 06, 2009 1:28 PM
To: VWNC
Subject: [vwnc] Subsystem framework needs a "postrequisites" method

 

The subsystem framework appears to have been designed to be

pluggable. However, it falls short in one area. If one needs to insure that

a subsystem activates “before” an existing subsystem then the

#prerequisites method of the existing subsystem must be modified to

make it happen. If there were a #postrequisites method then modification

of the existing #prerequisites method would not be required.

 

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

 

IMPORTANT NOTICE
Email from OOCL is confidential and may be legally privileged.  If it is not intended for you, please delete it immediately unread.  The internet cannot guarantee that this communication is free of viruses, interception or interference and anyone who communicates with us by email is taken to accept the risks in doing so.  Without limitation, OOCL and its affiliates accept no liability whatsoever and howsoever arising in connection with the use of this email.  Under no circumstances shall this email constitute a binding agreement to carry or for provision of carriage services by OOCL, which is subject to the availability of carrier's equipment and vessels and the terms and conditions of OOCL's standard bill of lading which is also available at http://www.oocl.com.

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc