The Communications Language PEPE # Introduction
Four simple concepts called Push,Pipe,Pull,Pump describe communications components. Lets give a first person description of what the component sees.
Pipe models storing information.
Pump models processing information.
Doing a small bit of thinking about those four ideas:
the Pump is fully active, having total responsibility for information handling.
This pair can be viewed conceptually as made from the other pair.
You have now seen the fu
There are two:
This tells us that we are only going to need pumps and pipes to build a system, and then think about which parts will need to be active and which passive when operating the system.
Before devising a BUILD language, which surely will be very complex, it might might HELP to list the components in the right order.
If you are ready, remember that to construct a written language you typically give the alphabet, a dictionary of the words, which are a selection of strings from the alphabet, and a grammar which shows the syntax for sentences. It is very complicated.
You now know the entire language.
Its easy to write a composition of any length:
It is not very hard to use this language, as there are only two sentences of any particular length, determined by the first letter!
Oh, I forgot the dictionary:
There are four words:
You may not be used to the fact that the grammar is already determined by the letters used, and you can think afterwards about what the author might have had in mind.
For example I write epepe.
I might mean exactly that
maybe I meant leh, ship it to be processed and sent back!
If you meant one of those things you could use words to say so!
This grammar is simple, but it is ambiguous!
We have just learned the entire language PEPE. If you are ready for meaning call for HELP.
You do not need a plan, just hand the builder a p or an e to start, along with enough supplies.
It is not a joke to make this observation, it is to emphasize that the language describes the abstract structure not because it uses words carefully but because it deliberately leaves out detail that is not directly related to the purpose. It focusses on what has to be done rather than on how it will be done.
Communications infrastructure is frequently revised as decisions are made as to who will do what and where. Remote Processing and Remote Storage possibilities change sometimes faster than the weather, and an ability to decide exceptly where the e and p will be placed determines which parts will serve as h and l. There are details, such as the size of components, and the relationship to the environment where the system will go whichare exceptionally important, but are to be decided after it is understood what the basic structure needs to be. Proper understanding of the basics
can have dramatic effects early, and especially later as the network needs to be reconfigured.
The model fits communications infrastructure nicely, especially in empasizing that there may be
descriptions`and even uses you did not anticipate. Communications networks often cross roads, rivers, oceans, and exist in outer space, but they all use versions of the components discussed.
There seems to be a lack of responsibility so far; who sees that all the pushes and pulls are actually done, and done properly in proper synchronizarion?
That is up to the operator, and we will devise a new language, not quite so complex, which will introduce the concepts Accept and Create and will therefore be called ACAC.