unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: guile-user <guile-user@gnu.org>
Subject: Re: [ANN] guile-mqtt-0.1.1 released
Date: Sun, 10 Nov 2024 21:47:31 +0100	[thread overview]
Message-ID: <CAA2Xvw+JhbD8k_9ovPwJytsZ=tEt2Bx8JdDFXWE8VMaVzdVMxw@mail.gmail.com> (raw)
In-Reply-To: <CAA2Xvw+fMxQwpHGjYbaAqKm+gAtGUh_LopsrQrWsaAVU=1mC9w@mail.gmail.com>

 * a tarball:

https://github.com/mdjurfeldt/guile-mqtt/releases/download/v0.1.1/guile-mqtt-0.1.1.tar.gz

* the git repository:
     https://github.com/mdjurfeldt/guile-mqtt
<https://github.com/mdjurfeldt/guile-mqqt>


On Sun, Nov 10, 2024 at 9:43 PM Mikael Djurfeldt <mikael@djurfeldt.com>
wrote:

> Guile MQTT provides bindings for the libmosquitto MQTT client
> library. The bindings are written in GOOPS
> (https://www.gnu.org/software/guile/manual/html_node/GOOPS.html)
> and rely on lower-level bindings created by NYACC directly and
> automatically from mosquitto.h.
>
> This release adds support for new options in connect:
>
> #:bind-address #:tls-cafile #:tls-capath #:tls-certfile #:tls-keyfile
> The guile-mqqt bindings align with GOOPS style, which means short
> method names. (The specialization is done through the arguments.)
>
> The user can extend the client class by inheritance.
>
> Example:
>
> This example, as well as the Guile libmosquitto bindings themselves,
> are inspired by the Chicken Scheme mosquitto bindings
> (http://wiki.call-cc.org/eggref/5/mosquitto) by Dmitrii Kosenkov.
>
> (use-modules (mosquitto client))
>
> (let ((client (make-client #:on-connect
>                           (lambda (client err)
>                             (if (not (eq? err MOSQ_ERR_SUCCESS))
>                                 (abort err)
>                                 (display "Yay, we are connected!"))))))
>   (set! (disconnect-callback client)
>         (lambda (client err)
>           (if (not (eq? err MOSQ_ERR_SUCCESS))
>             (display "Unexpected disconnect..."))))
>
>   (set! (message-callback client)
>         (lambda (cl msg)
>           (display (string->append "Topic: " (topic msg)
>                                    "Payload:" payload msg))
>           (publish client "topic2" "message received, thanks!")))
>   (connect client "localhost" #:username "mqtt-admin" #:password "mypass")
>   (subscribe client "topic1")
>   (loop-forever client))
>
> See further examples under the directory examples (
> https://github.com/mdjurfeldt/guile-mqqt/tree/main/examples).
> Guile MQTT maturity is beta level.
>
>  Guile MQTT is free software; the full source distribution is available
> through
>
> * a tarball:
>
> https://github.com/mdjurfeldt/guile-mqqt/releases/download/v0.1.1/guile-mqtt-0.1.1.tar.gz
> <https://github.com/mdjurfeldt/guile-mqqt/releases/download/v0.1.0/guile-mqtt-0.1.0.tar.gz>
>
> * the git repository:
>      https://github.com/mdjurfeldt/guile-mqtt
> <https://github.com/mdjurfeldt/guile-mqqt>
>
>


      reply	other threads:[~2024-11-10 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 20:43 [ANN] guile-mqtt-0.1.1 released Mikael Djurfeldt
2024-11-10 20:47 ` Mikael Djurfeldt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA2Xvw+JhbD8k_9ovPwJytsZ=tEt2Bx8JdDFXWE8VMaVzdVMxw@mail.gmail.com' \
    --to=mikael@djurfeldt.com \
    --cc=guile-user@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).