|
|||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||
Page Content
1. Core data flow managment.1. Core data flow managment. | |
The !plug object is the do-all core node which allows you to make any or all of your code a dynamic, highly stable and reflective piece of software.
Having many APIs share this same core engine, will allow you to leverage and allow many parts of your software to cooperate, in ways you might not have thought possible.
Important NOTE!
This is an alpha release and the liquid API, although in a Beta Candidate state, might change without notice.
2. Just what is a !plug ? | |
Basically, a !plug allows you to create a relationship or dependency between things and define what processing occurs, whenever some data ends up flowing to and out of the !plug.
!plugs by default, do not process anything until their content is needed by their relatives.
3. One class, several behaviours. | |
There are several ways you can link up or use a !plug out of the box:
This is explained in more detail in the reference page, but at this point, its really only necessary to know that the same allocated object can be used to store, process, filter, synchronize, signal, mirror, and other combinations of these processes.
The plug is a very handy class which allows you to make auto-processing networks of data.
The above is all possible with lazy computing and push or pull type of data flow, depending on setups and needs.
4. Where do I go from here? | |
For a quick example on how to setup and use liquid's plug node, you can go to the quickstart
For an indepth coverage (which will expand as time permits), you can go to the plug reference
page last updated: 2-Jan-2007
