> On 01-02-2018, at 5:02 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> 
> On Thu, Feb 01, 2018 at 03:02:45PM -0800, tim Rowledge wrote:
>> More improvements to MQTTClient; thanks to John we caught an issue with QOS 2 publishing. And discovered that the mosquitto broker will actually pass on invalid UTF-8 topic strings (really - a single byte 192 was sent by someone on the test.mosquitto.org open broker), so we had to cope with such nonsense.
>> 
>> Version 23 on squeaksource.com/MQTTClient and listed in SqueakMap.
>> 
> 
> Thanks for the update. It looks like the unit tests require a running broker
> on host amtiskaw, is there a way that we might mock this out or similate it
> in the image?  I suspect that a real broker would be a non-trivial thing to
> implement but some kind of fake broker to support the unit tests might not
> be too bad.

Hmm, a good point that I hadn’t thought to address. Logically speaking it ought to be possible to connect instead to test.mosquitto.org or some other public broker. The problem then becomes making the broker send the appropriate packets, something I think I simply cheated on during initial testing. By installing the mosquitto package on my mac mini I also got a commandline client that I could use to trigger actions. Doing this right will probably involve some Actual Thinking. Oh dear...


tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: EF: Emulate Fireworks