Service Guides on AngularTS

Making HTTP requests with the $http service

Mon, 01 Jan 0001 00:00:00 +0000

Use $http for application HTTP calls when you need request configuration, response transforms, interceptors, or integration with AngularTS services.

This guide focuses on workflows. Exact call signatures and exported interfaces live in TypeDoc:

Basic Requests

$http.get<User>('/api/users/42').then(({ data }) => {
 this.user = data;
});

Use a full request config when method, URL, headers, params, timeout, response type, or upload handlers need to be assembled together.

$http({
 method: 'POST',
 url: '/api/users',
 data: { name: 'Ada' },
 headers: { 'X-Trace': traceId },
}).then(({ data }) => {
 this.user = data;
});

Query Parameters

params are appended to the URL using $httpParamSerializer.

Decoupled Messaging

Mon, 01 Jan 0001 00:00:00 +0000

AngularTS has two messaging models:

$eventBus is an application-wide PubSub instance for decoupled communication, including messages from non-Angular code.
Scope events ($scope.$on, $scope.$emit, $scope.$broadcast) travel through the scope tree and are best for parent/child communication.

Exact $eventBus method signatures live in TypeDoc:

Inject $eventBus when a publisher and subscriber should not know about each other.

class CartService {
 static $inject = ["$eventBus"];

 constructor(private $eventBus: ng.PubSub) {}

 addItem(product: Product, quantity: number) {
 this.$eventBus.publish("cart:item-added", { product, quantity });
 }
}

class HeaderController {
 static $inject = ["$eventBus", "$scope"];

 cartCount = 0;

 constructor($eventBus: ng.PubSub, $scope: ng.Scope) {
 const unsubscribe = $eventBus.subscribe("cart:item-added", () => {
 const view = $scope["$ctrl"] as HeaderController;

 view.cartCount += 1;
 });

 $scope.$on("$destroy", unsubscribe);
 }
}

subscribe() returns an unsubscribe function. Keep that function and call it during teardown, especially from long-lived services, directive controllers, or manually bootstrapped integrations.

Real-Time Communication

Mon, 01 Jan 0001 00:00:00 +0000

AngularTS provides five building blocks for real-time and compute-heavy work:

$sse for Server-Sent Events.
$websocket for bidirectional WebSocket connections.
$webTransport for HTTP/3 WebTransport sessions with datagrams and streams.
ng-worker for JavaScript work in a Web Worker.
ng-wasm for loading WebAssembly modules.

Exact service and connection signatures live in TypeDoc:

Server-Sent Events

$sse creates a managed EventSource connection. It handles query parameters, JSON message parsing, heartbeat detection, automatic reconnection, and clean shutdown.

Typed REST Resources

Mon, 01 Jan 0001 00:00:00 +0000

$rest wraps a REST backend with a small typed resource client. By default it uses $http; pass a custom backend when a resource should read from another data source or compose network and cache behavior.

Exact method signatures live in TypeDoc:

Register a resource

Register shared resources in a config block. The provider stores resource definitions before the application starts, then the $rest factory uses the live $http service at runtime.

Client-Side Routing

Mon, 01 Jan 0001 00:00:00 +0000

AngularTS has two routing layers. $location manages the browser URL and history directly. $state works at the application level with named states, parameters, resolves, and transition hooks.

Exact routing API signatures live in TypeDoc:

Work With The URL

Use $location when code needs to inspect or change the raw URL.

$location.path(); // "/dashboard"
$location.search(); // { tab: "overview" }
$location.hash(); // "summary"
$location.url(); // "/dashboard?tab=overview#summary"
$location.absUrl(); // "https://app.example.com/dashboard?tab=overview#summary"

Setter methods return $location, so related URL changes can be chained.

Cookies And Browser Storage

Mon, 01 Jan 0001 00:00:00 +0000

AngularTS provides $cookie for typed, injectable cookie access and $window for direct browser storage access. Prefer injected services over globals so unit tests can replace browser APIs without patching window or document.

Exact cookie API signatures live in TypeDoc:

Read Cookies

$cookie decodes keys and values, parses document.cookie, and caches the parsed cookie map until the browser cookie string changes.

const token = $cookie.get("session_token");

const prefs = $cookie.getObject<UserPreferences>("user_prefs");

const all = $cookie.getAll();

Use get() for raw string values and getObject() only for cookies you control and know contain JSON.

Service Guides on AngularTS

Making HTTP requests with the $http service

Basic Requests

Query Parameters

Decoupled Messaging

Publish and subscribe

Real-Time Communication

Server-Sent Events

Typed REST Resources

Register a resource

Client-Side Routing

Work With The URL

Cookies And Browser Storage

Read Cookies