[paho-dev] Python MQTT client publish.single/multiple blocks indefinitel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[paho-dev] Python MQTT client publish.single/multiple blocks indefinitely?

From: Tony DiCola <tony@xxxxxxxxxxxxxx>
Date: Fri, 16 May 2014 14:56:07 -0700
Delivered-to: paho-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/paho-dev>
List-help: <mailto:paho-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/paho-dev>, <mailto:paho-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/paho-dev>, <mailto:paho-dev-request@eclipse.org?subject=unsubscribe>

Hey all, sorry if this is a known issue but is it by design that the publish.single or multiple functions are supposed to block indefinitely? I noticed the source for them connects, sends messages, and then calls client.loop_forever() so execution never returns back to the caller. How is a client application supposed to use these functions?

Follow-Ups:
- Re: [paho-dev] Python MQTT client publish.single/multiple blocks indefinitely?
  - From: Tony DiCola
- Re: [paho-dev] Python MQTT client publish.single/multiple blocks indefinitely?
  - From: Roger Light

Prev by Date: Re: [paho-dev] FW: [mqtt] Statements of Use
Next by Date: Re: [paho-dev] Python MQTT client publish.single/multiple blocks indefinitely?
Previous by thread: [paho-dev] FW: [mqtt] Statements of Use
Next by thread: Re: [paho-dev] Python MQTT client publish.single/multiple blocks indefinitely?
Index(es):
- Date
- Thread

Breadcrumbs