My apologies.  Wrong Dave!

Charlie Youakim
Partner


cell: 651-343-4692
fax:  888-804-1783
web: www.passportparking.com





On Wed, Jul 20, 2011 at 5:31 PM, Charles Youakim <
[email protected]> wrote:

> Thanks for the time Dave.  I'm going to check out the API.
>
> We will definitely be using your software.  The Gears software sounds
> great.  Let me know what you can sell the IP30 for.  We will be low quantity
> at the outset.  An order of 5 would be likely.
>
> Charlie Youakim
> Partner
>
>
> cell: 651-343-4692
> fax:  888-804-1783
> web: www.passportparking.com
>
>
>
>
>
> On Wed, Jul 20, 2011 at 5:27 PM, Dave Cridland <[email protected]> wrote:
>
>> On Tue Jul 19 21:19:15 2011, XMPP Extensions Editor wrote:
>>
>>> The XMPP Extensions Editor has received a proposal for a new XEP.
>>>
>>> Title: Whitespace Keepalive Negotiation
>>>
>>
>> FWIW, this one seems sensible for the XSF to adopt.
>>
>> I'd like to make some observations:
>>
>> 1) I think the negotiation should be more like resource binding - the
>> client offers a suggestion, the server sets the interval based on that
>> suggestion. I don't see a need for a back-and-forth where the client's value
>> is rejected as being out of range.
>>
>> 2) If either party sends any data, including whitespace, the timer MUST be
>> restarted.
>>
>> 3) Typically, I'd expect a client to negotiate a high keepalive, and then
>> issue the whitespace itself, in order to control transmission timing. (A
>> mobile client will want to send all its keepalive traffic at once).
>>
>> 4) Servers SHOULD use XEP-0199 or XEP-0198 to actively solicit traffic
>> from silent clients, and SHOULD only terminate the connection of
>> unresponsive clients, rather then merely silent ones.
>>
>> Dave.
>> --
>> Dave Cridland - mailto:[email protected] - xmpp:[email protected]
>>  - 
>> acap://acap.dave.cridland.net/**byowner/user/dwd/bookmarks/<http://acap.dave.cridland.net/byowner/user/dwd/bookmarks/>
>>  - http://dave.cridland.net/
>> Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
>>
>
>

Reply via email to