The document discusses how web pages work. It explains that HTML or XHTML is used to write web pages which are saved as text files. These files are uploaded to a web server from a local computer. When a user enters a URL, their request is routed to the appropriate web server which locates the file and sends it back to the user's browser to be displayed. Factors like the browser, screen size/resolution, color depth, and whether JavaScript is enabled can affect how a web page is displayed.
GWT Overview And Feature Preview - SV Web JUG - June 16 2009Fred Sauer
Overview of Google Web Toolkit (GWT) and GWT 2.0 Feature Preview, presented at the Silicon Valley Web Java User Group on June 16 2009 at the Googleplex in Mountain View, CA
This presentation is based on the first chapter of our textbook Fundamentals of Web Development. The book is published by Addison-Wesley. It can be purchased via http://www.amazon.com/Fundamentals-Web-Development-Randy-Connolly/dp/0133407152.
This book is intended to be used as a textbook on web development suitable for intermediate to upper-level computing students. It may also be of interest to a non-student reader wanting a single book that encompasses the entire breadth of contemporary web development.
This book will be the first in what will hopefully be a textbook series. Each book in the series will have the same topics and coverage but each will use a different web development environment. The first book in the series will use PHP.
To learn more about the book, visit http://www.funwebdev.com.
GWT Overview And Feature Preview - SV Web JUG - June 16 2009Fred Sauer
Overview of Google Web Toolkit (GWT) and GWT 2.0 Feature Preview, presented at the Silicon Valley Web Java User Group on June 16 2009 at the Googleplex in Mountain View, CA
This presentation is based on the first chapter of our textbook Fundamentals of Web Development. The book is published by Addison-Wesley. It can be purchased via http://www.amazon.com/Fundamentals-Web-Development-Randy-Connolly/dp/0133407152.
This book is intended to be used as a textbook on web development suitable for intermediate to upper-level computing students. It may also be of interest to a non-student reader wanting a single book that encompasses the entire breadth of contemporary web development.
This book will be the first in what will hopefully be a textbook series. Each book in the series will have the same topics and coverage but each will use a different web development environment. The first book in the series will use PHP.
To learn more about the book, visit http://www.funwebdev.com.
In this talk we will explore how to organize component-centric code splitting with server side rendering and universal data fetching in React, when your application becomes large enough.
Talk description: When you have a large enough application, a single large bundle with all of your code becomes a problem for startup time. You need to start breaking your app into separate bundles and load them dynamically when needed.
How to split a single bundle into multiple is a well-solved problem with tools like Browserify and Webpack.
But now you need to find places in your application where you can decide to split off into another bundle and load it asynchronously. You also need a way to communicate between server and client, and organize server side rendering and implement universal data fetching for your application.
Even React Router team failed with this task
“We’ve tried and failed a couple of times”(https://reacttraining.com/react-router/web/guides/code-splitting/code-splitting-server-rendering)
I will show you how to solve this problem, we will use a great library called React Loadable.
Also, we will look at some solutions which you can achieve with React Router v4 and why they are not the best one.
For this talk, you will need some knowledge in React, Babel (ES6), Node, Webpack 2, Redux, and little bit React Router v4.
In this presentation, I have shown how a webpage is loaded on your viewport after you request for the same. The process is simple. Once you click on the URL, the browser makes a request to the webserver. The request is processed by the webserver.
Web server files the response to the request and sends it to the browser. The requested page is sent to the web browser. The browser then loads and renders the page content. The requested page is then shown on the viewport.
Gear6 and Scaling Website Performance: Caching Session and Profile Data with...Gear6
This is a presentation given on April 14, 2009 to a select group of current memcached users. It includes survey results of how the dynamic web has given rise to the distributed caching tier, describes the growing popularity of memcached, provides poll results from memcached users and offers overview of the Gear6 Web Cache solution. Gear6 will be at the 2009 MySQL Conference at booth #218. Or visit us at Gear6.com.
The initial working implementation of getDisplayMedia() is available in the latest canary of Chromium(v70.0.3531.0).
What is it used for and why do we need a new API for screen sharing?
Is there going to be cross-browser API compatibility? Will it find its way into adapter.js?
Are there new security risks that come along with this new way of doing screen sharing?
How are browser/user permissions handled and is there going to be a need for a plug-in as today in Chrome?
Presentation given to the UK WebSphere User Group on 24 April 2016 giving a recap and update on integration between WebSphere Application Server and Docker. It covers both Liberty and the traditional application server.
STP204 Pinterest Pins AWS! Running Lean on AWS Once You've Made It - AWS re: ...Amazon Web Services
When you’re starting out, it’s not worth putting a lot of effort into optimizing your costs; you should put your time into growing your business. But as your infrastructure grows, it becomes worthwhile to optimize your use of AWS resources. Ryan Park from Pinterest’s technical operations team presents how they have optimized their infrastructure costs as their site has exploded in popularity.
In this talk we will explore how to organize component-centric code splitting with server side rendering and universal data fetching in React, when your application becomes large enough.
Talk description: When you have a large enough application, a single large bundle with all of your code becomes a problem for startup time. You need to start breaking your app into separate bundles and load them dynamically when needed.
How to split a single bundle into multiple is a well-solved problem with tools like Browserify and Webpack.
But now you need to find places in your application where you can decide to split off into another bundle and load it asynchronously. You also need a way to communicate between server and client, and organize server side rendering and implement universal data fetching for your application.
Even React Router team failed with this task
“We’ve tried and failed a couple of times”(https://reacttraining.com/react-router/web/guides/code-splitting/code-splitting-server-rendering)
I will show you how to solve this problem, we will use a great library called React Loadable.
Also, we will look at some solutions which you can achieve with React Router v4 and why they are not the best one.
For this talk, you will need some knowledge in React, Babel (ES6), Node, Webpack 2, Redux, and little bit React Router v4.
In this presentation, I have shown how a webpage is loaded on your viewport after you request for the same. The process is simple. Once you click on the URL, the browser makes a request to the webserver. The request is processed by the webserver.
Web server files the response to the request and sends it to the browser. The requested page is sent to the web browser. The browser then loads and renders the page content. The requested page is then shown on the viewport.
Gear6 and Scaling Website Performance: Caching Session and Profile Data with...Gear6
This is a presentation given on April 14, 2009 to a select group of current memcached users. It includes survey results of how the dynamic web has given rise to the distributed caching tier, describes the growing popularity of memcached, provides poll results from memcached users and offers overview of the Gear6 Web Cache solution. Gear6 will be at the 2009 MySQL Conference at booth #218. Or visit us at Gear6.com.
The initial working implementation of getDisplayMedia() is available in the latest canary of Chromium(v70.0.3531.0).
What is it used for and why do we need a new API for screen sharing?
Is there going to be cross-browser API compatibility? Will it find its way into adapter.js?
Are there new security risks that come along with this new way of doing screen sharing?
How are browser/user permissions handled and is there going to be a need for a plug-in as today in Chrome?
Presentation given to the UK WebSphere User Group on 24 April 2016 giving a recap and update on integration between WebSphere Application Server and Docker. It covers both Liberty and the traditional application server.
STP204 Pinterest Pins AWS! Running Lean on AWS Once You've Made It - AWS re: ...Amazon Web Services
When you’re starting out, it’s not worth putting a lot of effort into optimizing your costs; you should put your time into growing your business. But as your infrastructure grows, it becomes worthwhile to optimize your use of AWS resources. Ryan Park from Pinterest’s technical operations team presents how they have optimized their infrastructure costs as their site has exploded in popularity.
2. Anatomy of a web page
• HTML or XHTML is the language used to
write web pages.
• HTML stands for Hypertext Markup
Language which is basically a language that
you can use to markup or format hypertext.
• XHTML or HTML pages can be written in
word processing programs or in
WYSIWYG programs like Dreamweaver.
• All information in a web page is saved as
text including links to other pages and
images.
3. Anatomy of a web page
Text paths indicate where images
can be found
Live text is included as text
Colors are indicated by number
4. Anatomy of a web page
blog.html The text file is edited and saved on
your local computer.
The files and folders of your
website are uploaded to a web
server via an ftp program.
blog.html
QuickTime™ and a
decompressor
blog.html
are needed to see this picture.
~sweeneys QuickTime™ and a
decompressor
are needed to see this picture.
~sweeneys
Your local
computer Remote
web server
5. How a web page is delivered
Domain QuickTime™ and a
decompressor
Name
are needed to see this picture.
Server
Web
Server Users
QuickTime™ and a
decompressor
blog.html
are needed to see this picture.
~sweeneys
Step 1
User enters in URL
6. URL: Uniform Resource Locator
http://www.mccc.edu/~sweeneys/blog.html
Protocol Domain name Directory File name &
(hypertext (folder name) type
transfer
protocol)
7. How a web page is delivered
Step 2
Domain QuickTime™ and a
decompressor User request is
Name
are needed to see this picture.
routed to a Domain
Server Name Server
Web
Server Users
QuickTime™ and a
decompressor
blog.html
are needed to see this picture.
~sweeneys
8. How a web page is delivered
Step 3
Domain Name Server
translates domain Domain QuickTime™ and a
decompressor
name into IP address Name
are needed to see this picture.
and routes the
request to correct Server
web server
7 0 .1
3 3 .1
.1
Web 1 98
u=
c. ed Users
Server mc
c
w .
ww
QuickTime™ and a
decompressor
blog.html
are needed to see this picture.
~sweeneys
9. How a web page is delivered
Domain QuickTime™ and a
decompressor
Name
are needed to see this picture.
Server
Web
Server Users
QuickTime™ and a
decompressor
blog.html
are needed to see this picture.
~sweeneys
Step 4
198.133.170.1 Web server locates
the correct folder &
file. If no file is
specified it will display
the index.html file.
10. How a web page is delivered
Domain QuickTime™ and a
decompressor
Name
are needed to see this picture.
Server
Web
Server Users
QuickTime™ and a
decompressor
are needed to see this picture.
blog.html
198.133.170.1 Step 5
Web server sends the
file back to user
11. How a web page is delivered
Domain QuickTime™ and a
decompressor
Name
are needed to see this picture.
Server
Web
Server Users
QuickTime™ and a
decompressor
are needed to see this picture.
Step 6
User’s web browser
198.133.170.1 interprets HTML and
displays it
12. User display factors
What are some of the
factors that make a
web page display
differently?
13. User display factors
Browser
Internet Explorer
Firefox
Safari
Chrome
Mozilla
Opera
Netscape
AOL
PDA Browsers
Courtesy of W3.org
14. User display factors
Screen size & resolution
• 240x160
• 320x240
• 480x320
• 640x480
• 800 x 600
• 1024 x 768
• Larger
Courtesy of W3.org
15. User display factors
Color depth
• Most computers 24/32 bits:
16,777,216 colors
• Older computers/laptops 16bits:
• 65,536 colors
• Handheld 8 bit: 256 colors
Courtesy of W3.org
16. User display factors
Javascript
• On - most computers
• Off - some work computers
Courtesy of W3.org
17. User display factors
Gamma
• PC - 2.2 (darker)
• Mac - 1.8 (lighter)
Courtesy of Creative Bits