Should A Navigation And A Refresh Show The Same Page? Frontend First podcast

Artwork

Technology Web Ember Software Development Design Web Development Tech Software Development Frontend Ryan Toronto Sam Selikoff JavaScript Emberjs

Indhold leveret af Frontend First, Sam Selikoff, and Ryan Toronto. Alt podcastindhold inklusive episoder, grafik og podcastbeskrivelser uploades og leveres direkte af Frontend First, Sam Selikoff, and Ryan Toronto eller deres podcastplatformspartner. Hvis du mener, at nogen bruger dit ophavsretligt beskyttede værk uden din tilladelse, kan du følge processen beskrevet her https://da.player.fm/legal.

Frontend First « »
Should a navigation and a refresh show the same page?

1y ago 45:05

Del

MP3•Episode hjem

Indhold leveret af Frontend First, Sam Selikoff, and Ryan Toronto. Alt podcastindhold inklusive episoder, grafik og podcastbeskrivelser uploades og leveres direkte af Frontend First, Sam Selikoff, and Ryan Toronto eller deres podcastplatformspartner. Hvis du mener, at nogen bruger dit ophavsretligt beskyttede værk uden din tilladelse, kan du følge processen beskrevet her https://da.player.fm/legal.

Ryan and Sam talk about how to invalidate Next.js’ client-side cache when a different session makes changes to backend data, and ultimately discuss whether clicking a link to a URL vs. hitting refresh on that same URL should render the same page if no backend data has changed.

Topics include:

0:00 - Intro
1:00 - Suspense boundary identity and the Await component
11:07 - How to refresh RSC using a Server Action
27:17 - The difference between a navigation and a page refresh

Links:

… continue reading

196 episoder

#Technology #Web #Ember #Software #Development #Design #Web Development #Tech #Software Development #Frontend #Ryan Toronto #Sam Selikoff #JavaScript #Emberjs

Artwork

Should a navigation and a refresh show the same page?

212 subscribers

published 1y ago

Del

MP3•Episode hjem

Indhold leveret af Frontend First, Sam Selikoff, and Ryan Toronto. Alt podcastindhold inklusive episoder, grafik og podcastbeskrivelser uploades og leveres direkte af Frontend First, Sam Selikoff, and Ryan Toronto eller deres podcastplatformspartner. Hvis du mener, at nogen bruger dit ophavsretligt beskyttede værk uden din tilladelse, kan du følge processen beskrevet her https://da.player.fm/legal.

Ryan and Sam talk about how to invalidate Next.js’ client-side cache when a different session makes changes to backend data, and ultimately discuss whether clicking a link to a URL vs. hitting refresh on that same URL should render the same page if no backend data has changed.

Topics include:

0:00 - Intro
1:00 - Suspense boundary identity and the Await component
11:07 - How to refresh RSC using a Server Action
27:17 - The difference between a navigation and a page refresh

Links:

… continue reading

196 episoder

#Technology #Web #Ember #Software #Development #Design #Web Development #Tech #Software Development #Frontend #Ryan Toronto #Sam Selikoff #JavaScript #Emberjs

Alle episoder

×

Velkommen til Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

Lyt til 500+ emner