Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.5. Cloud Server
The ip.buffer can fetch source data from the Cloud Server running Scannex scripts. This is
useful where the information is being generated by a device on the Internet and the data
needs to be pulled safely into the ip.buffer for local delivery or anaylsis.
Cloud Server / Script
Markers
“
None
” – just stores the files as-is.
“
Use {cloud…}
” – applies the {cloud begin...} and {cloud end...
} markers
“
Use {cloud…}+CRLF
” – applies the {ftp} begin and end
markers on a separate line.
[Use {cloud…}+CRLF]
The Markers are in the form:
{cloud begin,
time
,
file,size
}
Where:
“time” is the date and time (local buffer time) in the form yyyymmddhhmmss.
“file” is the filename the Cloud server is about to push
“size” is the content length for the HTTP transfer
The data is then processed through the ip.buffer’s record detector (which can include
further modification such as adding a date time prefix etc). At the end of the file transfer
a suffix is appended to the memory store:
{cloud end,
time
,
file,size
}
10.6. None
The source setting “None” will disable the input channel completely.
However, the storage for that channel can still be used. For example another channel may
split its data with a Lua script and store half of the data in this channel.
Page 71
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
10.5. Cloud Server
The ip.buffer can fetch source data from the Cloud Server running Scannex scripts. This is
useful where the information is being generated by a device on the Internet and the data
needs to be pulled safely into the ip.buffer for local delivery or anaylsis.
Cloud Server / Script
Markers
“
None
” – just stores the files as-is.
“
Use {cloud…}
” – applies the {cloud begin...} and {cloud end...
} markers
“
Use {cloud…}+CRLF
” – applies the {ftp} begin and end
markers on a separate line.
[Use {cloud…}+CRLF]
The Markers are in the form:
{cloud begin,
time
,
file,size
}
Where:
“time” is the date and time (local buffer time) in the form yyyymmddhhmmss.
“file” is the filename the Cloud server is about to push
“size” is the content length for the HTTP transfer
The data is then processed through the ip.buffer’s record detector (which can include
further modification such as adding a date time prefix etc). At the end of the file transfer
a suffix is appended to the memory store:
{cloud end,
time
,
file,size
}
10.6. None
The source setting “None” will disable the input channel completely.
However, the storage for that channel can still be used. For example another channel may
split its data with a Lua script and store half of the data in this channel.
Page 71
