Perl-Sensitive Sunglasses | |
PerlMonks |
Architecture advice, proxy or rebroadcast websocketby Your Mother (Archbishop) |
on Jan 15, 2020 at 22:41 UTC ( [id://11111462]=perlquestion: print w/replies, xml ) | Need Help?? |
Your Mother has asked for the wisdom of the Perl Monks concerning the following question: I got some great advice for putting together my websocket client here: Mixing asynchronous data feed with synchronous program flow control. And it’s working well. 10,000 foot view: I am consuming a stock price stream. This is a paid service that only allows one connection and it is somewhat fragile due to a short timeout period, a dearth of documentation, and no built-in caching/reconnecting. None of my plans breach the user agreement/contract; that’s not me. I don’t want to write a cache/queue. I want to leave the stream alone and uncluttered with a bunch of synchronous calls that might throw exceptions or otherwise cause trouble; separation of concerns. I also want to test multiple versions of code against the single stream concurrently. I could record and play back data but that’s a pain, a disk hog, and it doesn’t address the fragility/complexity or any possible application of code against live data. My ideas have been–
So… I guess the last one. :P
Back to
Seekers of Perl Wisdom
|
|