Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)

I don't think this is a problem for RTC web to resolve. This is the same
problem that someone building an IM or email client for a web browser will
need to deal with. Some type of push notification framework is needed to
implement this and it might be something for W3C to standardize as a
solution for this problem.
_____________
Roman Shpount

On Thu, Sep 15, 2011 at 1:39 PM, Randell Jesup <randell-ietf@jesup.org>wrote:

> On 9/15/2011 10:34 AM, Roman Shpount wrote:
>
>> The only potential problem with mobile applications and javascript based
>> signaling code is the effect of maintaining registrations for long periods
>> of time while waiting for a call on battery life and network utilization. A
>> regular SIP library can be designed is such a way that the device will go
>> into sleep mode and will wake up when a SIP packet is received. JavaScript
>> will need to open a connection to a server and send ping messages at
>> regular, fairly short, intervals, that will cause device to wake up every
>> time ping message needs to be sent and to consume both power and network
>> capacity. Such applications, running for the long periods of time can
>> seriously decrease battery lifetime. On the other hand, doing this during an
>> active call has a negligible effect on both power consumption or network
>> utilization, since device is already running and sending media.
>>
>
> +1
>
> Any suggested solutions, other than "require (native) SIP"?   (Since
> SIP-in-JS would I assume fall into the case above.)
>
> --
> Randell Jesup
> randell-ietf@jesup.org
>
>
> ______________________________**_________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/**listinfo/rtcweb<https://www.ietf.org/mailman/listinfo/rtcweb>
>