CTtext writes text as-you-type to CloudTurbine. With every update, the full-length text file is written. This enables a very powerful text editing and streaming capability. As a user edits anywhere in the file, results are seen by streaming viewers. In this manner, viewers are able to watch the development of a document over time. As our first streaming text-based utility, CTtext has been useful in assisting CloudTurbine development and debugging. We encourage its use as-is or as a springboard for other text-based streaming applications:
- CloudTurbine-based chat
- annotate data in other CloudTurbine channels
- provide closed-captioning for CloudTurbine video channels
- facilitate distributed teaching
See our on-line demo using CTtext and CTstream.
The screenshot below shows a sample CTtext session. The user has entered several lines of text in the text area.
Text is displayed in near real-time using WebScan:
CTtext settings support customized destination and delivery options:
- The user specifies the output folder and channel name.
- Data may optionally be streamed using FTP.
- The user may either automatically flush data to the output folder at the indicated interval or chose to manually click the Flush button (located below the text area on the main CTtext window) when they wish to output data.
For the example shown below, data is written to a local folder, being automatically flushed (as a ZIP file) every 5 seconds.
Organization of the output data for our example is show in Windows File Explorer (below). ZIP files are written to disk at a rate corresponding to our specified “flush interval” (note, however, that the exact timestamps on the output ZIP files depend on the pacing of our typing).
Setting “flush interval” to “Max responsiveness” immediately flushes the document to disk as an uncompressed (non-ZIP) file with every edit (i.e., with every character you add or remove, a new data file will be written out). You can tailor your “real time” responsiveness by adjusting “flush interval”. Using a low “flush interval” value (or, at the extreme, setting it to “Max responsiveness”) provided a more “real time” experience to downstream viewers, however there will be more numerous files written to the file system. Using a larger value of “flush interval” increases the delay between typing text in the CTtext interface and having this data saved to a ZIP file on the file system – less of a “real time” experience however there will be fewer output files. Thus, there is a trade-off between “real time” responsiveness and number of files written to the file system.
Using any of the “flush interval” settings will capture every document edit (i.e., the document will be saved with each character that is added or removed). However, as explained above, there is a trade-off between “real time” responsiveness and number of files written to the file system. In contrast, using “Manual flush on button click” will only store the document content when you click the “Flush” button (located on the main panel just below the edit window). In this mode, you have complete control of both when the file is written to disk and what is included in each saved document.