BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
X-WR-TIMEZONE:America/Phoenix
BEGIN:VEVENT
DTSTART:20131019T170000Z
DTEND:20131019T181500Z
SUMMARY;ENCODING=QUOTED-PRINTABLE:An Hour (or so) at the SPA - Stephen J. Bodnar
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Single-page Applications or SPAs are all the rage these days. What are they? Are they right for you?=0D=0A=0D=0ASingle-page Applications are web sites that let visitors move through the app without a page refresh. The application logic is pushed down to the client and the application pulls data as required. The application can maintain state and it might use local storage.=0D=0A=0D=0AThe concept of SPAs has been around since the early 2000's but lately they seem to be the favored approach for greenfield web applications. Not so long ago, there was a lot of talk about how "desktop" applications could never be replaced with web applications. In the past, using traditional HTML approaches, this was a safe bet. Today, using SPAs built with modern JavaScript libraries, current HTML and the latest CSS techniques, it may just be possible to replace a desktop application with a web application.=0D=0A=0D=0AIn this session we'll look at the purpose of an SPA and discuss the suitability of this approach for various applications. We'll look at some of the popular JavaScript frameworks that are instrumental in developing Single Page Applications. =0D=0A=0D=0AWe'll also discuss the pros and cons of this approach. While it might be appealing to reduce server round-trips while delivering more responsive, fluid and interactive web pages, you'll also take on the responsibility for making sure things like back and forward buttons still behave the way the user would expect.=0D=0A=0D=0ATo put a handle on all these concepts, we'll build a simple SPA that will collect some data, validate it and store it to a database.
LOCATION;ENCODING=QUOTED-PRINTABLE:Elliott
UID:SWFOX20131019T170000Z
PRIORITY:3
END:VEVENT
END:VCALENDAR