User Agent - Revision history

Atheros at 08:52, 23 November 2012

2012-11-23T08:52:59Z

Atheros at 15:35, 2 October 2012

2012-10-02T15:35:44Z

Atheros: Created page with "Bitmessage user agents are a modified browser user agent with more structure to aid parsers and provide some coherence. The user agent strings are arranged in a stack with the..."

2012-10-02T15:34:45Z

Created page with "Bitmessage user agents are a modified browser user agent with more structure to aid parsers and provide some coherence. The user agent strings are arranged in a stack with the..."

New page

Bitmessage user agents are a modified browser user agent with more structure to aid parsers and provide some coherence. The user agent strings are arranged in a stack with the most underlying software listed first.

Basic format:

/Name:Version/Name:Version/.../

Example:

/PyBitmessage:0.2.2/Corporate Mail System:0.8/
/Surdo:5.64/surdo-qt:0.4/

The version numbers are not defined to any strict format, although this guide recommends:

* Version numbers in the form of Major.Minor.Revision (2.6.41)
* Repository builds using a date in the format of YYYYMMDD (20110128)

For git repository builds, implementations are free to use the git commitish. However the issue lies in that it is not immediately obvious without the repository which version proceeds another. For this reason, we lightly recommend dates in the format specified above, although this is by no means a requirement.

Optional -r1, -r2, ... can be appended to user agent version numbers. This is another light recommendation, but not a requirement. Implementations are free to specify version numbers in whatever format needed insofar as it does not include (, ), : or / to interfere with the user agent syntax.

An optional comments field after the version number is also allowed. Comments should be delimited by parenthesis (...). The contents of comments is entirely implementation defined although this BIP recommends the use of semi-colons ; as a delimiter between pieces of information.

Example:

/cBitmessage:0.2(iPad; U; CPU OS 3_2_1)/AndroidBuild:0.8/

Reserved symbols are therefore: / : ( )

They should not be misused beyond what is specified in this section.

* / seperates the code-stack
* : specifies the implementation version of the particular stack
* ( and ) delimits a comment which optionally separates data using ;

← Older revision		Revision as of 08:52, 23 November 2012
Line 32:		Line 32:
	* : specifies the implementation version of the particular stack		* : specifies the implementation version of the particular stack
	* ( and ) delimits a comment which optionally separates data using ;		* ( and ) delimits a comment which optionally separates data using ;
		+
		+
		+	----
		+	<small>This page was heavily derived from a page written by Amir Taaki and Patrick Strateman. Thanks be to them.</small>

@@ Line 19: / Line 19: @@
 Optional -r1, -r2, ... can be appended to user agent version numbers. This is another light recommendation, but not a requirement. Implementations are free to specify version numbers in whatever format needed insofar as it does not include (, ), : or / to interfere with the user agent syntax.
-An optional comments field after the version number is also allowed. Comments should be delimited by parenthesis (...). The contents of comments is entirely implementation defined although this BIP recommends the use of semi-colons ; as a delimiter between pieces of information.
+An optional comments field after the version number is also allowed. Comments should be delimited by parenthesis (...). The contents of comments is entirely implementation defined although this document recommends the use of semi-colons ; as a delimiter between pieces of information.
 Example: