creation of server protocol

000000000000001
100000000000111
110000011111000
111000000000000
000000000001110

*
the information flow that came
from timeline mergers and unit
zero point modulations and AI
can now be transported from the hardware
by server via the to be created protocol
*

*
within the margin of error caused by creation
we can estimate the volume
this can then be used to adjust the protocol
all this should be done, do not go beyond protocol limitation
a bigger protocol than needed would make for more volume
as the gaps will be filled.
*

*
we have found that data will evolve to the size of volume
thus having more volume means more data after transport
causing or creating more eventual damage.
*

*
one can make a larger protocol than estimated
with the addition of a sub server data collector
this will record the changes and additions
even if it is merged within the data
*

*
though this method is controversial
for it may be a cause of changes
rather than just a collector and recorder
*

*
to avoid contamination keep the protocol close to the estimated volume
do not go under the initial volume estimates.
make sure the container can accomodate all incomming data
and is de-contaminated.
*

*
do not mess with the server protocol once data transfers have started
this can only cause more damage.
*

*
do try to create a protocol that allows two way communication
this will be needed once the data flow is nearing completion
as a backup tool and conformation.
*

*
one way communication protocols have the drawback of not being sure
but are easier to build and maintain.
to create a protocol with two way communication is prefered.
*
*
*
server protocol 0001000111011xccHd12
data transfer flow volume 00110011Hd/12 4x
system check routine 3B_e4
syntex volume 8I/24d
bypass zeropoint modulation @3.664*2
return signal feedback @24Eide3
*

||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
////////system reboot required to start transfer\\\\\
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||

system shut down @23:40h

*
000000000000000
000000000100000
000100001000100
001011001101000
111010110110100