• RESTly
• Applications

Proto streamer is really good at HTTP 1.0 Streaming, but not very good for much else.

The proto streamer is implemented as the simplest possible piece of software to be very good at scalable streaming -- as for a protobuf application like a chat or a game.

Following this design program, the proto streamer creates a thread for each inbound tcp connection -- which is fine for long lived connections but not for other kinds of services. The proto streamer serves files in support of its applications, but is not a content server.

RESTly

Proto streamer is very RESTful. Its applications define HTTP Methods. So designing proto streamer applications is thinking from the HTTP request line as operations on paths, like "GET /foo" or "POST /bar".

Applications

Application methods extend a class named ps.Response, or one of its subclasses like ps.Buffer or ps.File.

An application method is loaded by name from the request path and method. The request "GET /foo" looks for a ps.Response class named "foo.Get", and likewise the request "POST /foo" looks for a response class named "foo.Post".

These classes may be most conveniently packaged under a directory named "classes" under the ps installation directory. See Startup for more details.

/p/

Next