- I changed the system to stop sending "raw" HTTP.
- I got megaphone to receive packets.
- I modified megaphone to send packets.
I thought there was a relatively straight-forward problem with ECM - specifically, it looked liked it was getting the equivalent of a null pointer exception. So I looked into the problem, fixed what seemed to be wrong and tried again.
This, of course, did not work.
So far as I can tell, megaphone is formatting the data correctly, it's sending the data, it just doesn't seem to be getting to ECM. At least all the time.
Sometimes, the packet arrives at ECM, I get a message and whatnot, but most of the time ECM just sort of sits there with an expectant look.
It's times like these that make me glad I've been giving shout outs to various countries, because this means I can forget my troubles by going out and drinking the celebrated alcoholic beverage of said country. I have to admit, however, that I'm partial to wine and beer --- I tend to avoid distilled stuff.
The current problem could make me change my ways in that vodka is looking awful good when I contemplate my troubles.
One thing I'm thinking of doing to test out the whole connection between ECM and megaphone is to create a "background" process for megaphone that periodically sends data to ECM. This would take the form of an "I'm alive!" style message that ECM would lovingly receive...and then promptly throw away. Nevertheless, it would give me a warm fuzzy that something was actually happening in terms of the connection between megaphone and ECM.
Next time: implementing this marvelous plan.
No comments:
Post a Comment