Currently this emits data only to standard out, but it will likely need to learn
how to drop this payload directly onto the eventbus in the near future
Now that I have something simple and functioning, this no longer needs to be
in the auctioneer
The fun work begins now, supporting custom messages known only to the auctioneer
for its needs, but passing those through EventBusClient
I originally tossed this approach since I believed that the awc +
actix-web-actors approach was unnecessarily complex. After experimenting a bit
with tungstenite, I believe that converting its high-level API into something
that I could work with in an asynchronous manner would require too much poking
around with tokio to be worth the effort.
I suppose I'll have to make do with the somewhat mid-level abstraction that
actix-web-actors provides me.
There's some refactoring I need to do in the server/eventbus module before
continuing, but this contains the initial cut of code necessary to create a new
inbox when a client connects that will map to that client name
R Tyler Croy