August 18th, 2015

@kvijesh there weren’t many international matches those days. They used to play in-between tours as well.

10:10 PM, Aug 18th, 2015 via Twitter for Android in reply to kvijesh

@kvijesh Sachin, Dravid, Laxman should have more runs.

9:38 PM, Aug 18th, 2015 via Twitter Web Client in reply to kvijesh

@gauntface Btw, SW file shows up in network panel for the first page load in Chrome Canary.

1:31 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface My bad. My bad. fetch() is working as expected. I have had “Disable cache” option on in devtools. Hence, the behavior.

1:30 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface Issues: 1. fetch() not honoring browser cache 2. SW download n registration not showing up in net panel (making life difficult)

1:09 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface #2 doesn’t seem valid to me now. When I request for sw.js explicitly, its just another file and not SW for browser.

1:07 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface 1. fetch() not honoring browser cache. 2. ‘fetch’ event being triggered for sw.js itself. Pls loop me in any tickets you create

1:03 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface Thanks for your time and your patience in responding on Twitter. Would love to do a hangout chat to clarify my understanding.

1:01 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface Had it used browser cache properly, expiry should not get updated for every browser refresh. Is that understanding correct?

12:53 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface When there is cache miss, I use fetch() to get the response. Wondering why is that fetch() call not using browser cache.

12:52 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface Network panel’s (from serviceworker) doesn’t seem to mean cache storage. Checkout console. fetch event triggered. Cache miss.

12:50 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface I am pretty confident that it is served by SW itself. Am I missing something here? pic.twitter.com/S01AK379nb

12:25 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface Yeah, thatz the trick I am using. My SW file is served from SW itself and its expiry keeps increasing by 4 hrs.

12:17 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@gauntface Is there anything wrong with my config here — adhiyan.in/sw.js

12:09 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@gauntface Another issue: I see that serviceworker file is also getting cached making updates difficult. I need to clear cache or incognito

12:09 AM, Aug 18th, 2015 via TweetDeck in reply to varunkumar

@psankar How is it different from git in terms of its architecture? I ll read abt it anyways.

12:05 AM, Aug 18th, 2015 via TweetDeck in reply to psankar

@gauntface @jaffathecake Thanks for pointing it out.

12:04 AM, Aug 18th, 2015 via TweetDeck in reply to gauntface

@psankar ohh ok. Interesting. But, it also has a downside of blotting your repo right.

12:03 AM, Aug 18th, 2015 via TweetDeck in reply to psankar

@psankar What are X refs?

12:02 AM, Aug 18th, 2015 via TweetDeck in reply to psankar