PureBasic Forums - English

@plouf, you are right: My somewhat bigger Programm compiles now smaller (tested with X64, ASM, identical options)
6.04 : 399K
6.10 : 1000K (x 2.7)
6.11 : 640K (x 1.6)

I can live with a Exe-BlowUps of less than x2 ..., 6.10 usually produced x3-5 for my projects, so I had skipped the 6.10.

Perfect, everything works fine now. :D
Then, I make my not so realistic MQTT speed tests, to scratch the limitations.

Setups:
- 4 Clients compiled .exe running (Two Tests with #USE_BASE64_PAYLOAD = #True or #False)
Logwinodw limited to 300 Lines to avoid speed loss with e.g. >1000 Lines
- 1 ...

Hi,
I was "out of order" for a few days, but now I tried a comparison regarding your suggestion.
I think I noticed about 20% better throughput if I complie the MQTT_Broker with #USE_BASE64_PAYLOAD = #False.
I cannot fully test it, because a problem occured:
Publishes from broker to clien appear to ...

.... tests are not really what I'd consider a typical use case for MQTT
You are right. But like I said, I just want to explore the limits. Later, publishes are only every 200-500ms over a real network (with pingtimes 2-20ms), but then I know that it will still work even if the host is briefly 90 ...

Hi again,
I don't get tired of playing around with your work :D
btw. When you receive #Error_BadUsernameOrPassword Or #Error_UnsupportedIdentifier it doesn't help to simply retry it ...
Absolutely, this was only for testing. I have started one or many of your clients in background and change ...

Here my simple solution to avoid having to restart the client when common problems arise.
That's enough for me, because the client side is only for testing purposes in the moment.
I've picked out a few errors that I think repeating connection attempts making sense and implemented it like this ...

That was the point I missed: Add the necessary things in MQTT_EventIncoming() / Case MQTT_Common::#MQTTEvent_Error
I'm sure I'll get it done now, but not until the weekend. thanx for your support

Hi again,
I created a simple client (based on your Client.pbi) for logging/testing. Everything is fine, but if I start the client before a broker can be reached,
there is only a log message ("Can't connect to Broker!") and never another connection attempt.
The same if broker is offline for a short ...

Ah, a good idea, I agree.

Very nice... the link in the first post now leads to the updated broker source V1.12.
But apart from the code addition you suggested above, the following line (Just a few lines above) was also changed:
Case #PUBLISH
If \PayLoad\BufferLengh >= 0 ; <== In V1.11 it was only > 0
i = \PayLoad ...

Yes, the error no longer occurs that way. (I was afraid to disturb something else in the broker doing it that simple way.)
My short solution works also, CopyMemory() has no problem with 0 length
CompilerIf #USE_BASE64_PAYLOAD
If (i) : Base64Decoder(\PayLoad\PayLoadBase64, *Buff + OffsetOf(HEADER ...

Now after some time I have probably found a small bug. (?)
Using two (or more) MQTT-Explorer-0.4.0-beta1.exe - instances running and connected via 127.0.0.1 to your broker.
( MQTT Client ID's: e,g, "mqtt-explorer-1" / "mqtt-explorer-2" )
If I do a ' publish topic' from either client without ...

Sorry for the late reply, and thanks for the retain addition in 'MQTT_Client.pbi'.
I don't have any other points at the moment for future updates.
Maybe one publish code sample in Client.pbi may help someone else,
or other application examples, I don't know.

I will create an application COM port ...

Big Thx, I look forward to future updates.

Hi,
I have downloaded the latest sources from https://hex0rs.coderbu.de/cgi-bin/hv.cgi?version=-1&id=127&ia=1923
and use this incredible work and the MQTT-Explorer-0.4.0 to get a feel for MQTT.
Working without any problems so far. 8) (PB6.04-X64 on Win10)

A few questions remain (using your ...