Internet Technologies Grade 12

How the web works under the hood — search technologies, web technologies, online applications, and how data is stored and processed online.

T3Term 3 · Internet & Web Technologies

Search Technologies

TypeDescription
Keyword searchMatches exact words in the query
Semantic searchUnderstands meaning and context behind words — interprets user intent, not just keywords
Mediated searchA middleman system filters results for a specific database or organisation (e.g. Google Scholar)
SEOSearch Engine Optimisation — techniques to make websites rank higher in search results (keywords, speed, mobile-friendly, backlinks)

Static vs Dynamic Websites

StaticDynamic
ContentFixed HTML — changes only if developer edits filesGenerated on demand from a database
DatabaseNoYes
ExamplesSimple portfolio, business info pageOnline shop, social media, news sites
Security riskLowHigher (SQL injection, data breaches)

Web Technologies

TechnologyRoleExample
HTMLStructure and content of web pagesHeadings, paragraphs, links, images
CSSVisual styling — colours, fonts, layoutBlue buttons, responsive grid
JavaScriptClient-side interactivity; runs in the browserForm validation, dropdown menus, AJAX
PHPServer-side scripting; processes forms, talks to databasesLogin authentication, database queries
SQLQuery and manage database dataSELECT user data, INSERT orders
XMLStructured data exchange between systemsProduct data feeds between websites
RSSAn XML-based feed format that lets users subscribe to a site and automatically receive new content as it is publishedNews headlines, blog posts, new podcast episodes

Storing Data Online

Running Instructions

Client-side (browser)Server-side (web server)
LanguageJavaScript, AJAXPHP, Python, Node.js
PurposeReal-time page updates, validation, animationsAuthentication, database access, processing
AJAXUpdates parts of a page without reloading—

The Role of Scripting Languages

A scripting language is what turns a plain, static page into a website that actually does something. Its role always splits into two halves — what happens instantly in the visitor's browser, and what happens back on the web server — and an online store is a good way to see both halves at work at once.

Client-side scripting (e.g. JavaScript)

Runs in the customer's own browser, so it can react instantly without waiting for the server. On an online store it could:

  • Validate the checkout form before it is submitted — e.g. checking that a cellphone number field isn't empty or that the quantity entered is a valid positive number — so the customer sees the error immediately, without a round trip to the server.
  • Update the shopping cart total the instant a customer changes a quantity, with no need to reload the page.
  • Show or hide extra product information (e.g. a "Read more" description) when clicked.
Server-side scripting (e.g. PHP)

Runs on the store's web server, so it's the only place that can safely reach the database. On an online store it could:

  • Check the product database to confirm an item is still in stock before allowing checkout.
  • Calculate the order total and generate an order confirmation.
  • Securely process the customer's login and payment details.
  • Insert the new order into the database and update the stock level once payment succeeds.

HTTP vs HTTPS

HTTPHTTPS
EncryptionNone — data sent in plain textSSL/TLS encryption
PadlockNo padlock in browserPadlock icon shown
UseNon-sensitive public pagesLogin, banking, shopping — any sensitive data