In the end, there's not only two connections, which flip-flop (one always being
an active connection). But there are unlimited connections.
Every time a new request must be sent, a new connection is created, which sends
the request and then waits for a response.
If a new request must be sent, wh
Hi,
yes, "to" should be "from" in 7.2.
Concerning the xs:positiveInteger:
http://www.w3schools.com/schema/schema_dtypes_numeric.asp
I am not really sure if a positiveInteger is unbound and an unsignedInt is
limited to 32bit. I don't really understand the difference anyway.
Still, unsignedLong fe
Hi!
On Wed, Dec 11, 2013 at 1:12 AM, Peter Saint-Andre wrote:
>
> Lance has sent me an updated patch, which I have applied. The diff
> between 124rc1 and 124rc2 is here:
>
> http://xmpp.org/extensions/diff/api/xep/0124/diff/1.11rc1/vs/1.11rc2
I guess the 'to' attribute in section 7.2 (session cr
On Dec 10, 2013, at 3:06 PM, Christian Schudt wrote:
> Hi,
>
> I am new to this mailing list.
>
> I have been trying to implement BOSH in Java (client side) on basis of draft
> 1.10.
>
> I think the document is quite understandable.
>
> However, I ran into the following issues:
> - I did no
On 12/10/2013 02:36 PM, Lance Stout wrote:
The moral of the story is that you really only ever need two connections, and
you flip between the two whenever you need to send a stanza and the old
connection is sent whatever traffic has been buffered.
I'm curious, what's the rationale for the fli
> In the 1.11 version I don't really understand the diagram under point 4. Too
> many "empty" bodies.
> - What is the left side and the right side?
> - From "X" to "*" is one HTTP request? Then why is there a long time no
> request (but many pipes |)?
We may need to include some more labeling i
Hi,
I am new to this mailing list.
I have been trying to implement BOSH in Java (client side) on basis of draft
1.10.
I think the document is quite understandable.
However, I ran into the following issues:
- I did not understand the HTTP pipelining stuff, which is now removed :)
- The 'rid' an
On 11/27/13 8:23 AM, Winfried Tilanus wrote:
> On 08-11-13 23:40, Peter Saint-Andre wrote:
>
> Hi,
>
>> Sitting here at IETF 88 with Lance Stout, I'm reminded to finally
>> apply the collected patch he sent me to incorporate all the hard
>> work that various folks on this list did earlier this
Hello Teemu
Thanks for the feedback. The description in §7.3.2 was perhaps a bit
minimalistic. I extended it as follows:
Event messages could be published using Publish-Subscribe. Unless there's
absolute control of who can subscribe to the information published in this
manner, the information
Hi Peter.
Section 7.3.2 Publish/Subscribe describes: "Event messages could be
published using Publish-Subscribe. But, even more care should be taken
to log only information that can be published openly. If there's risk
for sensitive information to be logged, the publish/subscribe pattern
should be
Hello Waqas
It is correct that I looked at XEP-0122 when describing data types of tags,
this is the reason I forgot to add the namespace declaration, which would have
been the correct thing to do. I didn't want to limit the types used to those
referred to in that XEP, but if possible it would b
11 matches
Mail list logo
