I want to avoid reinventing the wheel but, at the same time, I don't want to burden simple projects with a complex framework that provides 10,000% more than I need. I like little pieces, tied together to make bigger pieces. Even when using VB, while others would write monolithic systems that compiled to 6 or 8 meg, I wrote lots of 100-200K apps that worked together to make a system. That makes it easier to build different systems from different parts.
So, to put things into a different context lets look at the need to print a file. Imagine for a moment that the existing print capabilities didn't exist. How would you write something like this in Rebol. Especially if there are printers to which you direct certain print jobs because they can for example handle postscript and others can't. Other printer capabilities come into play depending on the requirements for printing this certain type of file. You want to be able to initiate the job, so a form will probably come up. The job ticket containing the information is put somewhere so we need a unique task number generated by the system itself. A message is sent to the appropriate event manager indicating a new job notice. The event manager schedules the task. The event manager processes the task and sends a message to a daemon/service on some remote machine behind the scenes. We can query the status of the task and find it is waiting on a certain resource for example. When the task is complete we are notified that the task is complete, successfully, in error, or someone cancelled the task. We might want to be able to resume the task for various reasons. If the system goes down, any jobs not yet entered into the system will be noticed upon event manager startup and are not lost. Does IOS or Rebol do this? Dick Download NeoPlanet at http://www.neoplanet.com -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
