BinaryProcedureEncode (Stringlist subroutine) - Revision history

JAL: /* Examples */

2012-10-30T21:51:50Z

Examples

← Older revision		Revision as of 21:51, 30 October 2012
Line 40:		Line 40:
	%procData:add('END PROCEDURE')		%procData:add('END PROCEDURE')
	</p>		</p>
	The actual saving of the data to a procedure is not shown, though the example <var>Stringlist</var> could easily be passed to a <var>Daemon</var> object <var>[[Run (Daemon function)\|Run]]</var> method to create the procedure.		The actual saving of the data to a procedure is not shown, though the example <var>Stringlist</var> could easily be passed to a <var>[[Daemon class\|Daemon]]</var> object <var>[[Run (Daemon function)\|Run]]</var> method to create the procedure.

	==See also==		==See also==
	{{Template:Stringlist:BinaryProcedureEncode footer}}		{{Template:Stringlist:BinaryProcedureEncode footer}}

JAL at 21:09, 23 October 2012

2012-10-23T21:09:41Z

← Older revision		Revision as of 21:09, 23 October 2012
Line 16:		Line 16:

	==Usage notes==		==Usage notes==
	<ul><li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.		<ul>
			<li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.

	<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.		<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.
	<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.<~~br/~~>'''Note: '''The <var>[[BinaryProcedureDecode ~~(Stringlist_function)\|BinaryProcedureDecode]]~~</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding.
	~~<li>The <var>BinaryProcedureEncode</var> method is available in <var class="product">Sirius Mods</var> Version 6.7 and later~~.</ul>		<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.

			<p>'''Note: '''The <var>BinaryProcedureDecode</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding. </p>

	==Examples==		==Examples==

JALWiccan: 1 revision

2012-10-23T21:06:19Z

1 revision

← Older revision	Revision as of 21:06, 23 October 2012
(No difference)

JALWiccan: 1 revision

2012-10-23T21:06:18Z

1 revision

← Older revision		Revision as of 21:06, 23 October 2012
Line 18:		Line 18:
	<ul><li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.		<ul><li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.
	<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.		<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.
	<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.<br/>'''Note: '''The <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding.~~</blockquote>~~		<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.<br/>'''Note: '''The <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding.
	<li>The <var>BinaryProcedureEncode</var> method is available in <var class="product">Sirius Mods</var> Version 6.7 and later.</ul>		<li>The <var>BinaryProcedureEncode</var> method is available in <var class="product">Sirius Mods</var> Version 6.7 and later.</ul>

JALWiccan: 1 revision

2012-10-23T21:05:05Z

1 revision

← Older revision	Revision as of 21:05, 23 October 2012
(No difference)

JAL2: /* Examples */

2012-10-23T21:05:04Z

Examples

← Older revision		Revision as of 21:05, 23 October 2012
Line 18:		Line 18:
	<ul><li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.		<ul><li>All errors in <var>BinaryProcedureEncode</var> result in request cancellation.
	<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.		<li>This method (along with the <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method) facilitates converting data in a string into the format used for storing binary data in procedures by <var class="product">[[Janus Web Server]]</var>. This format is necessary if binary data is to be stored in <var class="product">Model 204</var> procedure files because standard procedure formats are not amenable to storing binary data.
	<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.<~~blockquote~~>The <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding.</blockquote>		<li>All data in the binary procedure encoding is wrapped in container data that makes it convenient to store the data in a procedure. By default, the data is also stored in base64 encoding, which represents the data as common displayable characters, making it even more convenient to work with. The convenience of base64 encoding does have a cost, however: it takes four bytes of encoded data to represent three bytes of binary data. In addition, on storage and retrieval, the data must be converted from binary format to base64 encoding and vice versa, which will require some CPU (although probably not a dramatic amount). If the benefits of base64 encoding are determined to not be worth the costs, the second parameter of <var>BinaryProcedureEncode</var> can be set to <var>False</var> to cause the data not to be base64 encoded.<br/>'''Note: '''The <var>[[BinaryProcedureDecode (Stringlist_function)\|BinaryProcedureDecode]]</var> method and all other facilities that read the binary procedure encoding format will automatically determine whether the data is base64 encoded or not and do the appropriate decoding.</blockquote>
	<li>The <var>BinaryProcedureEncode</var> method is available in <var class="product">Sirius Mods</var> Version 6.7 and later.</ul>		<li>The <var>BinaryProcedureEncode</var> method is available in <var class="product">Sirius Mods</var> Version 6.7 and later.</ul>

JAL2: /* Examples */

2012-04-11T21:49:15Z

Examples

← Older revision		Revision as of 21:49, 11 April 2012
Line 22:		Line 22:

	==Examples==		==Examples==
	~~<ol><li>~~The BinaryProcedureEncode method takes data from a string and places it on a <var>Stringlist</var>, from which it could then be stored in a procedure. In the following example, a GIF (graphical image) is retrieved from another web server using a <var class="product">[[Janus Sockets]]</var> HTTP helper request and then moved onto a <var>Stringlist</var> with the special binary procedure encoding:		The BinaryProcedureEncode method takes data from a string and places it on a <var>Stringlist</var>, from which it could then be stored in a procedure. In the following example, a GIF (graphical image) is retrieved from another web server using a <var class="product">[[Janus Sockets]]</var> HTTP helper request and then moved onto a <var>Stringlist</var> with the special binary procedure encoding:

	<p class="code">%req is object httpRequest		<p class="code">%req is object httpRequest
Line 36:		Line 36:
	%procData:add('END PROCEDURE')		%procData:add('END PROCEDURE')
	</p>		</p>
	The actual saving of the data to a procedure is not shown, though the example <var>Stringlist</var> could easily be passed to a <var>Daemon</var> object <var>[[Run (Daemon function)\|Run]]</var> method to create the procedure.~~</ol>~~		The actual saving of the data to a procedure is not shown, though the example <var>Stringlist</var> could easily be passed to a <var>Daemon</var> object <var>[[Run (Daemon function)\|Run]]</var> method to create the procedure.

	==See also==		==See also==
	{{Template:Stringlist:BinaryProcedureEncode footer}}		{{Template:Stringlist:BinaryProcedureEncode footer}}

Dme: /* Examples */

2011-02-07T22:43:59Z

Examples

← Older revision		Revision as of 22:43, 7 February 2011
Line 29:		Line 29:
	%procData is object stringList		%procData is object stringList
	...		...
	~~</p>~~
	%resp = %req:get		%resp = %req:get
	%gif = %resp:content(1)		%gif = %resp:content(1)

Wiccan: 1 revision

2011-02-07T21:23:52Z

1 revision

← Older revision	Revision as of 21:23, 7 February 2011
(No difference)

Wiccan: 1 revision

2011-02-07T21:23:51Z

1 revision

← Older revision		Revision as of 21:23, 7 February 2011
Line 28:		Line 28:
	%gif is longstring		%gif is longstring
	%procData is object stringList		%procData is object stringList
	~~<p class="code">~~...		...
	</p>		</p>
	%resp = %req:get		%resp = %req:get