Provide some level of statistics ? about tiny_httpd HOT 8 CLOSED

And this should be optional ?

from tiny_httpd.

This should definitely be outside of tiny-httpd, I think it just has to provide some core primitives (like number of active connections), and maybe some instrumentation.

if we get an optional wrap_query parameter (maybe a begin_query: ip -> port -> 'a and end_query: 'a -> unit pair), then you can instrument however you want: prometheus, tracy, hand rolled sqlite-based analytics, etc. Mechanism, not policy 😉

from tiny_httpd.

Of course a very basic statistics module can be provided alongside Tiny_httpd_utils, like Tiny_httpd_stats with exactly that kind of pair to pass to Tiny_httpd.create.

from tiny_httpd.

I like the idea of a wrapper for connection, the wrapper could have access to both the request and the response though ?
For the default stats, I think something usefull ought to write in a Db from which it is easy to compute average and so on... And therefore hard to provide a default. Except if you have something specific in mind ?

from tiny_httpd.

from tiny_httpd.

We already have an internal handler type, which could probably be compatible with a middleware type handler -> handler:

(* a request handler. handles a single request. *)
type cb_path_handler =
  out_channel ->
  byte_stream Request.t ->
  resp:(Response.t -> unit) ->
  unit

from tiny_httpd.

The middleware patch + example of stat in echo.ml solves this issue ?

from tiny_httpd.

yeah it's easy to done oneself. done.

from tiny_httpd.