Improving Message Delivery and Modularity, Making the System Packet Agnostic, Handling Edge Cases, and Creating a Library.

[Samshal]

Great job, @phalcorine, on your work so far on this repo! I think the architecture is flexible enough to be used for other purposes if we turn it into a library that's packet agnostic instead of tying it to a specific packet structure.

It seems like the current implementation has a dispatcher that queues failed requests due to network issues. However, there could be other factors, such as firewalls, that affect message delivery. In these cases, continuously attempting to send the message may not be effective, so we need to handle edge cases gracefully.

Overall, I believe this project has the potential to be extended to handle a variety of message delivery nuances. Starting with turning it into a library would be a great first step.

Please let me know what you think

[phalcorine]

Thanks for the compliments @Samshal 👍🏾

I like the idea of the implementation being package-agnostic. Also, there needs to be some refinements in determining when (and how frequent) do we retry the queue and also logging the cause of the errors when attempts fail (server-down, internet-connectivity, etc).

As for making it into a library, I think that would depend on how well it solves the problem at hand. But let's see how it goes...