vishnu8406/live_stream

Purpose

live_stream is a minimal browser-facing live-stream prototype. The repository exposes separate sender and receiver pages, suggesting a two-party media/session flow rather than a server application.

Entry Points

• Sender UI/session entry: sender.html

• Receiver UI/session entry: receiver.html

These standalone HTML files are the only executable application surfaces visible in the repository.

Sender Stage

sender.html is the producer-side boundary. It is expected to own capture or selection of stream content and initiation of a session toward a receiver. Any browser media APIs, connection setup, or signaling logic would be embedded in this page because no separate source modules are present.

Receiver Stage

receiver.html is the consumer-side boundary. It is expected to establish or accept a matching session and render/play the incoming live stream. Display and receiver connection lifecycle are therefore coupled in this page.

Primary Flow and Boundaries

The implied control/data path is:

1. A user opens sender.html and starts a stream/session.

2. Session/connection information must cross from sender to receiver through a mechanism implemented or manually mediated by the pages.

3. A user opens receiver.html, supplies or receives corresponding session information, and consumes the stream.

The sender/receiver split is the primary architectural boundary. No backend, API service, database, signaling server, package manifest, or deployment infrastructure is represented in the supplied tree.

Runtime and External Dependencies

The material runtime is a web browser serving or opening sender.html and receiver.html. Browser-provided media/network capabilities may be used, but the repository tree does not establish which APIs or external services are configured. README.md provides only the project name and no operational contract.