On Saturday, September 22, 2012 12:49:29 PM UTC+1, maarten wrote:
> .... if you suspect others could benefit from what you find, please report
> here (and maybe in the wiki).
> --Maarten
> On Saturday, September 22, 2012, Dano wrote:
>> Thanks David. I am relieved that Lift comet actor support works with
>> iOS6 - that explains the lack of alarm. I had jumped to a conclusion.
>> Next time I will check the demo site first.
>> I will do some more digging based on your reply to see if I can pry our
>> app loose on iOS6.
>> Dan
>> On Friday, September 21, 2012 3:57:35 PM UTC-7, David Pollak wrote:
>>> CometActors work fine on iOS 6. I just used http://demo.liftweb.net on
>>> my iPad and iPhone (both iOS 6). The comet actors stuff works perfectly.
>>> If you're having a problem with connection starvation, please see
>>> LiftRules.**maxConcurrentRequests. It will allow you to compute the
>>> maximum requests for a single session.
>>> You can also use the comet from random hostname feature to make sure
>>> each request comes to a different hostname which means you'll never have
>>> more than 1 Comet long poll to a given host.
>>> On Fri, Sep 21, 2012 at 3:21 PM, Dano <oleary...@gmail.com> wrote:
>>>> Tyler,
>>>> Thanks for your response.
>>>> I am a little surprised there is no alarm with respect to comet actors
>>>> being out of commission on iOS6, but maybe I am just not understanding the
>>>> situation.
>>>> Probably should have added some detail in the original post. Our site (
>>>> playknowsy.com) uses comet actors to support interactive game play
>>>> (just like our other site innovationgames.com which is referenced on
>>>> liftweb.net as an example site). We tuned our site for the iPad form
>>>> factor and touch interface. It also works great on desktop browsers too.
>>>> Our site playknowsy.com is currently DOA on iOS6 with respect to game
>>>> play (which is the main feature of the site). Any other site on the planet
>>>> which uses long polling is also DOA on iOS6. It may be that Apple sees the
>>>> error of their ways and fixes the problem (which I expect they will but it
>>>> is really hard to wait and do nothing in the meantime).
>>>> That said, I was hoping not to have to rewrite our site to use
>>>> websockets as an emergency fix (much as I like the solution it provides).
>>>> As to the caching content, are you implying I should I tweek the Lift
>>>> sources to change the comet actor POST to set the Cache-Control in the
>>>> header to "no-cache"?
>>>> I am just trying to figure out a "plan B" should Apple fail to come
>>>> thru.
>>>> Thanks again for hearing me out.
>>>> Dan
>>>> On Friday, September 21, 2012 1:05:06 PM UTC-7, Tyler Weir wrote:
>>>>> It looks like Safari on iOS6[3] supports Websockets[1].
>>>>> Also, check out this comment regarding caching content[2].
>>>>> [1] - http://en.wikipedia.org/**wiki**/WebSocket<http://en.wikipedia.org/wiki/WebSocket>
>>>>> [2] - http://stackoverflow.com/a/**1**2516555/456551<http://stackoverflow.com/a/12516555/456551>
>>>>> On Friday, September 21, 2012 2:28:45 PM UTC-4, Dano wrote:
>>>>>> Hello,
>>>>>> As mentioned on hacker news (http://www.realsoftwareblog.**c**
>>>>>> om/2012/09/ios-6-mobile-**safari**-web-applications.html<http://www.realsoftwareblog.com/2012/09/ios-6-mobile-safari-web-appli...>),
>>>>>> it looks like mobile safari is restricting the number of simultaneous open
>>>>>> http connections to 1 (down from the standard 2 all other browsers support).
>>>>>> The only guidance I have seen so far is from this post (
>>>>>> http://stackoverflow.com/**ques**tions/12506897/is-ios6-**safari-**
>>>>>> caching-ajax-results<http://stackoverflow.com/questions/12506897/is-ios6-safari-caching-aj...>)
>>>>>> which recommends adding a variable to the post which keeps the browser from
>>>>>> caching the result from the first long polling call and reissue the next
>>>>>> one. I am not exactly sure what this translates to for Lift apps with
>>>>>> comet actors.
>>>>>> Have any Lifters seen this problem and/or figured out an easy way to
>>>>>> deal with it?
>>>>>> Thanks in advance.
>>>>>> Dan
>>>>> --
>>>> --
>>>> Lift, the simply functional web framework: http://liftweb.net
>>>> Code: http://github.com/lift
>>>> Discussion: http://groups.google.com/**group/liftweb<http://groups.google.com/group/liftweb>
>>>> Stuck? Help us help you: https://www.assembla.com/wiki/**
>>>> show/liftweb/Posting_example_**code<https://www.assembla.com/wiki/show/liftweb/Posting_example_code>
>>> --
>>> Telegram, Simply Beautiful CMS https://telegr.am
>>> Lift, the simply functional web framework http://liftweb.net
>>> Follow me: http://twitter.com/dpp
>>> Blog: http://goodstuff.im
>>> --
>> --
>> Lift, the simply functional web framework: http://liftweb.net
>> Code: http://github.com/lift
>> Discussion: http://groups.google.com/group/liftweb
>> Stuck? Help us help you:
>> https://www.assembla.com/wiki/show/liftweb/Posting_example_code