promote gus/gemini types, handlers, middleware to gus package #11

New Issue

tjp · 2023-01-12T17:12:34Z

tjp commented

2023-01-12 17:12:34 +00:00

If we intend to add more protocols (#4, #5, #6, #7), we ideally want to be able to re-use code (handlers, middlewares) across the small web protocols.

If Handler and Middleware are going to be generic, they can't very well be defined in terms of gemini.Request and gemini.Response either, so those need to be promoted as well.

Currently our Request and Response types directly support io interfaces like Reader and WriterTo, but the gemini protocol specific code obviously has to be kept in gus/gemini, so there is separation needed.

If we intend to add more protocols (#4, #5, #6, #7), we ideally want to be able to re-use code (handlers, middlewares) across the small web protocols. If `Handler` and `Middleware` are going to be generic, they can't very well be defined in terms of `gemini.Request` and `gemini.Response` either, so those need to be promoted as well. Currently our `Request` and `Response` types directly support `io` interfaces like `Reader` and `WriterTo`, but the gemini protocol specific code obviously has to be kept in `gus/gemini`, so there is separation needed.

tjp added the

enhancement

label 2023-01-14 18:05:30 +00:00

tjp added this to the v1.0 milestone 2023-01-14 18:06:13 +00:00

tjp changed title from ~~promote `gus/gemini` types to `gus` package~~ to promote `gus/gemini` types, handlers, middleware to `gus` package

2023-01-16 17:12:36 +00:00

tjp self-assigned this 2023-01-16 17:12:40 +00:00

tjp modified the milestone from v1.0 to v0.5

2023-01-17 16:31:34 +00:00

tjp added a new dependency 2023-01-17 16:32:11 +00:00

#12 package-level documentation

tjp closed this issue