GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — GitHub - bert-github/SSE-Server: A server for sending Server-Sent Events (SSE) to web clients

BranchesTags
Open more actions menu

Latest commit

 

History

52 Commits
52 Commits

Folders and files

NameName
Last commit message
Last commit date
.gitignore
.gitignore
 
 
AUTHORS
AUTHORS
 
 
COPYING
COPYING
 
 
ChangeLog
ChangeLog
 
 
INSTALL
INSTALL
 
 
Makefile.am
Makefile.am
 
 
NEWS
NEWS
 
 
README
README
 
 
README.md
README.md
 
 
bootstrap.sh
bootstrap.sh
 
 
cexport.1
cexport.1
 
 
cexport.c
cexport.c
 
 
configure.ac
configure.ac
 
 
connectsock.c
connectsock.c
 
 
export.h
export.h
 
 
logger.c
logger.c
 
 
memmem.c
memmem.c
 
 
sse-server.1
sse-server.1
 
 
sse-server.c
sse-server.c
 
 

Repository files navigation

SSE-Server

SSE-Server implements an HTTP server that sends Server-Sent Events (see section 9.2 of HTML5) to connected web clients. (Typically: web pages with JavaScript that uses the EventSource API.)

SSE-Server supports SSL, but does not implement any form of authentication. (It is possible to use Apache or another web server as a reverse proxy and let that server handle the authentication.)

Receiving events

Web clients connect to this server and then keep the connection open, waiting for the SSE server to send them messages.

The server provides an arbitrary number of ‘channels’ and clients can subscribe to one or more of them, or to all of them. They then get the messages that are sent on the subscribed channels.

Sending events

Web clients that want to send messages to clients on one or more channels can connect to the server with a query at the end of the URL. The query contains the message type and the message data.

Messages to send can also be provided through a dedicated port of the server, separate from the port that web clients connect to. This ‘control port’ accepts simple text lines. (I.e., it does not accept HTTP.)

And a third way to send messages to web clients is by writing them to a FIFO file on the machine the server is running on. This FIFO accepts the same simple text lines as the control port.

Some examples

Let's assume the SSE-Server is running on host example.org and listening on port 8080 for URLs like this:

https://example.org:8080/my/sse/server

Then a client can subscribe to, e.g., the channels ‘color’, ‘number’ and ‘page’ by adding those to the path. The order does not matter:

https://example.org:8080/my/se/server/color/number/page

In SSE, each message must have a type (the event type) and a content (the event data), both of which are arbitrary text strings. To send a message of type ‘message’ with content ‘first’ to all clients on the ‘color’ channel, make a GET request to this URL:

https://example.org:8080/my/sse/server/color?message=first

You can send multiple messages to multiple channels in one go:

https://example.org:8080/my/sse/server/color/page?q1=go&q2=end

This sends two messages (type ‘q1’ with data ‘go’ and type ‘q2’ with data ‘end’) to both the color and page channels. (Clients subscribed to both channels will only get the messages once.)

To send those same two messages via the FIFO or the control port, write these four lines to them:

color/q1 = go
page/q1 = go
color/q2 = end
page/q2 = end

(Except that, unlike with the URL query above, clients subscribed to both the ‘color’ and ‘page’ channels will get the messages twice.)

White space at the start and end, and around the ‘=’, will be ignored.

To do this on the command line on Unix, assuming the FIFO is called ‘sse.fifo’, use a command such as this:

echo "color/q1 = go" > sse.fifo

On the FIFO and the control port, the event type ‘message’ is the default and can be omitted. E.g., the following two lines are equivalent.

channel/message = some data here
channel = some data here

Commands

Apart from messages, the server accepts two commands:

‘status’: This puts some information in the log file (if logging is enabled) with information about currently connected clients.

‘halt’: This disconnects all clients and stops the server. E.g.:

echo halt > sse/fifo

These commands can be given on the FIFO. The server normally does not accept them on the control port or in a query on the HTTP port, but there is an option to enable that.

Running under Apache

You can use Apache as a reverse proxy to an SSE-Server (for the HTTP port only, the control port does not use HTTP). This can be useful when running on a system that already has Apache running on the desired port, or to use Apache for authentication.

Choose a path prefix, e.g., ‘/my/sse/server’, choose a port (e.g., the default, 8080) and put this in the Apache configuration:

<Location "/my/sse/server">
  ProxyPass http://localhost:8080/my/sse/server
</Location>

Then run the server, e.g. like this:

sse-server -f sse-server.fifo -P 8085 -l sse-server.log

And use it as normal, but without the port 8080:

https://example.org/my/sse/server/channel71

Acknowledgments

SSE-Server was inspired by hasses by Péter Deák.

About

A server for sending Server-Sent Events (SSE) to web clients

Resources

Readme
License
Activity

Stars

3 stars

Watchers

1 watching

Forks

2 forks
Report repository

Releases

Packages

Contributors

Languages

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.