This document discusses the evolution of web applications from static HTML pages to single page applications (SPAs). Early web applications used static HTML pages that loaded entirely when requested, while dynamic pages loaded content from a database. JavaScript added interactivity but required page reloads to update. AJAX allowed updating parts of a page without reloading via XML/JSON. Native apps communicated with servers via APIs for new data. SPAs combine JavaScript, DOM manipulation, and AJAX to allow web browsers to behave like native apps, loading initial content and then updating dynamically without reloads. This avoids maintaining separate web and API code.
An Exploration of Frameworks – and Why We Built Our OwnAndrew Rota
Insights drawn from our recent process of evaluating the latest JS frameworks, why we rejected them all to build our own, and why you might consider doing the same.
Co-Presented with Matt DeGennaro on Thursday, March 26, 2015 at BostonJS (http://www.meetup.com/boston_JS/events/221038649/).
This is my March 8, 2001 pitch to Jeff Bezos on why Amazon ought to offer web services. I'm uploading it now because I'm referencing it in my forthcoming book, WTF: What's the Future and Why It's Up To Us, due from Harper Business in October 2017, and want people to be able to take a look at it. This is of historical interest only.
An Exploration of Frameworks – and Why We Built Our OwnAndrew Rota
Insights drawn from our recent process of evaluating the latest JS frameworks, why we rejected them all to build our own, and why you might consider doing the same.
Co-Presented with Matt DeGennaro on Thursday, March 26, 2015 at BostonJS (http://www.meetup.com/boston_JS/events/221038649/).
This is my March 8, 2001 pitch to Jeff Bezos on why Amazon ought to offer web services. I'm uploading it now because I'm referencing it in my forthcoming book, WTF: What's the Future and Why It's Up To Us, due from Harper Business in October 2017, and want people to be able to take a look at it. This is of historical interest only.
This is the week 1 presentation to express the basics of web development and design to masters candidates who embarked on a 13 week soup to nuts web marketing adventure.
Slides from the Google DevFest Istanbul 2014 talk 'Mobile apps in 100% pure Java'. Slides are meant as a helper for the presenter, and are not standalone.
Salesforce composite api mule soft connectorpqrs1234
Pain Points with Traditional Approach
What is Salesforce Composite API?
What an sObject is, Batch is and Composite Request is?
How to create nested records of the same type?
How to create multiple, unrelated records of the same type?
Limitations of the Salesforce composite connectors
Comparison between Batch, Composite Request and sObject Tree
Live Demo
Concocting an MVC, Data Services and Entity Framework solution for AzureSaltmarch Media
Often, technologies are demonstrated in their own little vacuums. In this session we'll put together a solution that combines Windows Azure, SQL Azure, Data Services, MVC and Entity Framework so that you can see how to create a solution completely hosted in the cloud.
Riscopriamo il mondo contadino della Maremma Settentrionalescuolabloggando
La scuola primaria Carlo Collodi ha partecipato a un concorso a premi per la tutela dei beni comuni e per il consumo responsabile con questa realizzazione
Overview of Alberta Helping Animals Society, A Canadian charity that helps provide vulnerable people in Edmonton and surrounding areas with access to veterinary care and other services for their companion animal.
This is the week 1 presentation to express the basics of web development and design to masters candidates who embarked on a 13 week soup to nuts web marketing adventure.
Slides from the Google DevFest Istanbul 2014 talk 'Mobile apps in 100% pure Java'. Slides are meant as a helper for the presenter, and are not standalone.
Salesforce composite api mule soft connectorpqrs1234
Pain Points with Traditional Approach
What is Salesforce Composite API?
What an sObject is, Batch is and Composite Request is?
How to create nested records of the same type?
How to create multiple, unrelated records of the same type?
Limitations of the Salesforce composite connectors
Comparison between Batch, Composite Request and sObject Tree
Live Demo
Concocting an MVC, Data Services and Entity Framework solution for AzureSaltmarch Media
Often, technologies are demonstrated in their own little vacuums. In this session we'll put together a solution that combines Windows Azure, SQL Azure, Data Services, MVC and Entity Framework so that you can see how to create a solution completely hosted in the cloud.
Riscopriamo il mondo contadino della Maremma Settentrionalescuolabloggando
La scuola primaria Carlo Collodi ha partecipato a un concorso a premi per la tutela dei beni comuni e per il consumo responsabile con questa realizzazione
Overview of Alberta Helping Animals Society, A Canadian charity that helps provide vulnerable people in Edmonton and surrounding areas with access to veterinary care and other services for their companion animal.
Per questo progetto i bambini della Scuola Primaria “Carlo Collodi” hanno incontrato i vigili del fuoco e imparato come affrontare i pericoli della vita quotidiana a scuola e come reagire in caso di terremoto e incendio. Un minicorso sulla sicurezza fatta di esercitazioni pratiche e insegnamenti teorici per seguire i piani di emergenza ed evacuazione della scuola con maggiore consapevolezza e tranquillità.
Tutto è nato lo scorso anno quando abbiamo accolto l’apertura straordinaria degli archivi storici comunali della Toscana e visto che stavamo lavorando sui documenti storici abbiamo visitato l’archivio storico del nostro Comune. Abbiamo così toccato con mano che gli archivi, anche e soprattutto a livello locale, sono in troppi casi istituzioni sconosciute ai cittadini che, a differenza di quanto avviene per musei e biblioteche, non li avvertono come patrimonio della collettività.
Vitali zaidman Do You Need Server Side Rendering? What Are The Alternatives?CodeValue
There are numerous strategies to choose from when building modern HTML-based apps today.
You can render it on the client-side, the server, or even generate it during build time.
You need to make a choice, and tools like Gatsby, Next.js, Angular Universal, ScullyIO, and NuxtJS can help you get there.
How do you make the right choice though? Why would you choose one over the other?
Join me in this session as we demystify the different approaches and discuss the trade-offs while exploring real-world examples.
A three hour tutorial I gave at PHP Quebec on the challenges, theory, and concepts behind making asynchronous JavaScript calls for Web 2.0 Applications using PHP
"AJAX = Asynchronous JavaScript and XML.
AJAX is a technique for creating fast and dynamic web pages.
AJAX allows web pages to be updated asynchronously by exchanging small amounts of data with the server behind the scenes. This means that it is possible to update parts of a web page, without reloading the whole page.
Classic web pages, (which do not use AJAX) must reload the entire page if the content should change.
JS Fest 2019/Autumn. Александр Товмач. JAMstackJSFestUA
Вы уже слышали о JAMstack, который пришел на смену SSR и SPA? Подход, который оптимизирует веб приложения так, что они ограничены только скоростью вашего интернет соединения. Никаких просадок при рендере на клиенте, никаких падений серверов от нагрузки, только SEO-friendly приложения без проблем с масштабируемостью.
JavaScript is the most widely used language cross platforms. This talk will analyze the security concerns from past to present with a peek to the future of this important language. This talk was presented as Keynote at CyberCamp Espana 2014.
2. The beginning of the beginning…
(early 1990s)
Request (GET) for a
Static HTML Page
Respond with requested
Static HTML Page
STATIC HTML PAGE
3. The beginning of the beginning…
(early 1990s)
Request (GET) for
another Static HTML
Page by clicking on a
Hyperlink
Respond with requested
Static HTML Page
FROM ONE PAGE TO ANOTHER
4. A little after the beginning of the beginning….
(mid 1990s)
Submit new order to the
server using an HTML
form
Store the order and respond
with a confirmation HTML
page.
FORM SUBMISSION (POST)
5. A little after the beginning of the beginning….
(mid 1990s)
Request for a Dynamic
Page showing all orders
so far…
Generate a dynamic html page
based on current data and
respond with that page.
DYNAMIC PAGES (GET)
6. Birth of a star… (1995)
Request for a Page
Respond with the page along
with its corresponding
JavaScript which adds
behavior to the otherwise
extremely boring and inactive
page.
JavaScript
7. Birth of another star… (1996)
Request for a Page
Respond with the page along
with its corresponding CSS
which gives a way to separate
structure from presentation.
CSS
8. The 3 stars that became super stars…
Structure Presentation Behavior
9. Exchange of new information with the server, after a page is
loaded, required a page refresh or use of browser plug-ins such as
Macromedia Flash, Java Applets, etc.
• Eg: While following a game, the sports page needed a refresh every 30
seconds so that a whole new page was generated by the server with the
latest scores.
• Eg: A chat session required a browser plug-in such as Java Applets which
allowed the display of new messages on the page.
• Eg: An interactive video game page required a browser plug-in such as
Macromedia Flash to allow the page to interact with other users.
The Big Limitation…
10. Enter the game changer (2005)…
Request for latest information
behind the scenes without
reloading the parent page using
just plain JavaScript and no
plug-ins.
Respond with information
requested that can be quickly
integrated into the parent page
by the browser without
reloading.
11. Enter the devilry… Native Apps (2007)
Request or send data in
the form of XML or JSON
while all the screens and
their rendering is handled
client-side.
Respond with the requested
data or acknowledge receipt
of new data from the client.
12. Too much happening server-side…
With the entry of Native Apps web applications now needed to
maintain two sets of code on the server-side…
1) One set of code to continue supporting web browsers which
required..
1) rendering of HTML pages with data pulled from the database.
2) acceptance of form data and responding with an acknowledgement
page.
2) Another set of code to exchange just data with Native Apps via
APIs. Pretty much every major feature that a web application
provided had to be made available also in the form of an API.
13. Need for better life…
Maintaining two sets of code doing more or less the same thing is
always a pain. How can we avoid it? Is it possible to come up with a
way where we only need to maintain one or the other?
Well… let’s think about it… all we have to do is make the web browser
behave like a Native App.
How can we do that?
Well… we have JavaScript which can render new elements based on
data. It can also allow content to be changed within an element in the
DOM.
And we have AJAX which allows new content to be brought in without
reloading the page…
So, all we need to do is to combine all these features!
15. A much better life…
Request or send data in
the form of XML or JSON
while all the screens and
their rendering is handled
client-side.
Respond with the requested
data or acknowledge receipt
of new data from the client.