> >1. Standard protocol framework: > > > > What does this mean? > >
> What is more though - you have tcp family protocols, but is that > sufficient? You want to communicate, right? You want two machines talk > one to each other? > >Great, so you have to build kind of a client, and > server. But then you want probably your server to understand some > commands? OK, so you build protocol, for your server communication. But > - that protocol will be probably useless for anyone else. So, I can > imagine tool, which will serve as communication matrix, dispatcher, call > it whatever. It should allow to: > - bind protocols on certain ports > - define callbacks for certain kind of events happening on port .... eg. > on-length, on-char-received, etc. > - define handlers > - define amount of child processes to be started (we have no threading yet) > - be dynamic. I don't accept anything not being able to dynamically > bind, unbind stuff at runtime, without the restart. > - watch the status - monitor > > So - if such framework would exist, if it would be good enough, most ppl > would concentrate upon it, and build stuff for it = central starting > base, unification, consistency. It should imo also become native part of > Rebol distribution. > Cheers, > -pekr- Sometimes, even I amaze myself at how slow I am when immersing into a new world so to speak. Let me say this: USER PROFILE: Information about users to provide capability to restrict. SYSTEM CONFIGURATION INFORMATION: An RDBMS centralized repository of information which results from the implementation of systems and their components. The information object types/nodes can consist of (but not limited to) these conceptual artefacts AP, JC, DT, EM, UI, JI, JN, RM, JE. Each named node of the preceding object types contains information as to its physical location, how to execute, and how to communicate with it in the case it is a service/process. JI - Job Initiator (usually a button on a GUI) submits tasks to be performed (JC). AP - APPLICATIONS - Arbitrary container of a large abstraction. JC - JOBCLASSES - Internalized services/processes for named tasks which might involve one or more steps to be performed and how to handle errors, etc. DT - DATATRANSFORMERS - Inputs/Outputs (grind the data) EM - EVENTMANAGER - Scheduler/dispatcher reacts to incoming message eventtype to execute a JC and its associated steps. UI - GUIS - A users view of the application world. JN: A flexible, configured methodology for notifying of success/failure/cancellation. JE: Control of network devices such as printers to prevent inadvertent mixing of outputs. RM: Someone has to guard the data and other resources to provide a shared/exclusive contract arrangement. CONFIGURATION LIBRARY: A software library which provides access to the centralized repository of information which describes the implementation of computer programs. MESSAGING LIBRARY: A software library which provides the capability for sending and receiving messages within the contrived application world. MESSAGE FORMAT (PROTOCOL): A simple format which includes a few fields of information to allow hi-level interpretation for purposes of routing through the application world. These could include sender, recipient, eventid, eventtype, and TEXT. The TEXT portion of the message may contain anything (even Rebol code) which is understandable to the target process/recipient. CENTRALIZATION OF CORPORATE POLICIES & PROCEDURES: The access of configuration information may result in the internalized automatic evaluation of embedded macros which may in turn refer to other portions of the information repository. This internal evaluation allows for centralization of policies and procedures within an organization. Think of a heirachical tree, where the leaves may refer to other (higherup) nodes for certain information, such as the shared directory location where executables are stored or which version to use of a CAD/CAM extraction tool, etc. QUESTION: When you say protocol, are you talking about a common messaging format or something else? QUESTION: When you are talking about framework, are you talking about an application architecture which provides persistent end-to-end task management? After all, Rebol is no different than Java, Tcl/Tk, Perl, and other well known languages. It is simply a language with certain powerful constructs. Without an overall application framework they are just languages. 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.
