shclisem
Simple HTTP Client Semaphore (by madman22)
mangos
mangos is a pure Golang implementation of nanomsg's "Scalablilty Protocols" (by nanomsg)
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
shclisem
Posts with mentions or reviews of shclisem.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-10.
-
Queuing up API requests with waitgroups?
A Semaphore might be your best best, check out the code in my repo, https://github.com/madman22/shclisem
-
handling http response
here is my example that uses a drop in replace to use a semaphore to limit the number of in flight requests: https://github.com/madman22/shclisem
-
Reconnect to a server
As long as the pub/sub is an interface, you can create your own implementation that has reconnection and backoffs. I made my own http client that is a drop in replacement for the standard library http client with added methods for more features. https://github.com/madman22/shclisem as an example
mangos
Posts with mentions or reviews of mangos.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-07.
- What would be a good message broker internal to my program?
-
Reconnect to a server
I'm writing a client application that uses https://github.com/nanomsg/mangos to connect to a server using the PUB/SUB protocol. I'm not sure how to handle server or network interrupts on the client. The application is just a for loop waiting for a message to arrive and the call a go routine to handle that message. Does anybody know a good example how to deal with network or server failures in GO? Or should the application just panic and let the OS create a new instance of the application? The client application will run as a daemon so users can not interact with it.