gofre VS sse

Maybe you can take a look over my framework https://github.com/ixtendio/gofre which respects all the golang standards and has similar performance like echo.

Maybe you can try https://github.com/ixtendio/gofre which is a web framework that respects the Golang standards, has a nice error management and in some cases performs better than Gin. On top of that the pattern matching is much richer and better than Gin or Echo

Hi sikoyo, and thanks for your appreciation. If it will be to compare with other popular frameworks, not only with Echo, it will be like: 1. The programming model is simple and natural. For example a GoFre handler returns a response or an error. The response is an interface with 4 methods, compared with Echo which provides a Context (an interface with 55 methods :) ). Imagine if you want to extend Echo with response compression how simple it is? In GoFre just implement a new Response that wraps the original response. See this implementation https://github.com/ixtendio/gofre/blob/main/response/compress.go for example Gin, another framework uses the same concept like Echo :) but at least in their case the Context is not an interface but a structure which contains a lot of fields which should not be there. The same problem here, how easy is it to extend it for your needs? 2. Another difference is in patch matching. GoFre supports approximately the same path matching as the Java Spring framework. For example if you have the following patterns:

You see, I've been using https://github.com/r3labs/sse to implement an SSE server handler, but I'm not using many of its features, such as auto replaying from the last event ID following a re-connect. And it imposes a concept of "streams" which are superfluous for my use case. Thus it may well be simpler to write my own handler.

I am thinking of using this package and there is a Client type that I think I can customize.