On Sat, 17 Nov 2001 01:58, Pratik Patel wrote: > >Not really. What I am saying is that currently the Application is > > responsible for deciding when Blocks will be started or shutdown or > > whatever. This is required because there may be interdependencies between > > blocks and so forth. So there is no way for a Block to shut itself down, > > what you really need to do is ask the application to shutdown the Block > > and it will take care of making sure it shutsdown according to the > > dependency rules etc. > > But do we want to make an interface to the block for start/stop/etc so > that we have a uniform way for the > application to start/stop blocks? I apologize in advance if this an > ignorant question, as I can't get to the > Avalon website to check the current block interface... connection > problems today (on my end, "Â$%^&* ISP).
Well I guess the point I am trying to get across is that you can't really shutdown an individual block in an application. You shutdown an application and it will shutdown the Blocks but at this stage there is no way to shutdown (or startup) an individual block. -- Cheers, Pete "Artists can color the sky red because they know it's blue. Those of us who aren't artists must color things the way they really are or people might think we're stupid." -- Jules Feiffer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>