Harlan Iverson wrote:
Actually the XEP does mention the GET request limit in 18.2, just below example 40 (emphasis mine):Although RFC 2616 does not limit the length of HTTP URIs, the runtime environment of the client might restrict the length of the URI that it can include in each GET request. [30 <http://www.xmpp.org/extensions/xep-0124.html#nt-id2266059>] In these cases the client MUST reduce the content of the <body/> element accordingly and send the remaining content in subsequent HTTP GET requests wrapped in new <body/> elements (with incremented 'rid' attributes). This is possible since, unlike Pure Syntax, with Script Syntax the connection manager *MUST treat the string of characters between the opening and closing <body> tags of each request as part of an octet stream instead of as a set of complete XML stanzas. The content of any one <body/> element MUST NOT be parsed in isolation from the rest of the stream*.My interpretation of this is that each <body> can contain partial stanzas including unclosed tags that are closed subsequent <body>s. xmpp4js does not currently do this, in part because I am unsure that I'm interpreting it correctly, and in part because I haven't experienced a limit (though it's probably a matter of time).An example illustrating this in the XEP would be useful.
I'm happy to add an example of this. /psa
smime.p7s
Description: S/MIME Cryptographic Signature
