Re: [ServiceWorker] Add cookie accessor/setter methods? (#707)

With navigator.connect one would need to implement a flow like:
- SW only ever serves a bootstrap page
- Bootstrap page signals to SW it is now ready to answer questions about
cookies or sends current cookies to SW
- SW replies with actual response
- Bootstrap upgrades to full page based on that.

Please lets not require hacks like this as the first thing privacy
sensitive people have to do when using SWs.


On Wed, Jun 10, 2015 at 6:55 AM Malte Ubl <malte.ubl@gmail.com> wrote:

> That isn't going to change that spinning up 3, 5, 20 or even 100 SWs on
> logout on a device with 256 MB of RAM will not work in a timely fashion.
>
> Maybe we could make the API read-only initially to reduce complexity.
> On Jun 10, 2015 6:42 AM, "Anne van Kesteren" <notifications@github.com>
> wrote:
>
>> That should be considerably easier once you can use service workers as a
>> service (through navigator.connect).
>>
>> —
>> Reply to this email directly or view it on GitHub
>> <https://github.com/slightlyoff/ServiceWorker/issues/707#issuecomment-110758206>
>> .
>>
>


---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/707#issuecomment-110765410