Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [sparkplug-wg] Unified Namespace

Thanks David,

We were considering all the levels and going all the way up to Cloud.

I’m interested in what you mentioned around the application functions are available that help ensure message delivery and notifications when they aren’t…could you give some examples please?

Thanks,

Kevin.

On Thursday, December 5, 2024, David Schultz <dschultz@xxxxxxxxx> wrote:

Depends on how you define a UNS. If you mean only Level 2 and below, like telemetry data, SpB is preferred. While it uses QoS 0, there are other application functions that help ensure message delivery and notifications when messages are not reeived.

 

David Schultz

G5 Consulting & Engineering Services

512 Westlawn Avenue | Mukwonago | Wisconsin | 53149

M +1 262.441.6109 | E dschultz@xxxxxxxxx

People | Process | Technology | Solutions | Results

 

 

From: sparkplug-wg <sparkplug-wg-bounces@eclipse.org> on behalf of Kevin Kilroy via sparkplug-wg <sparkplug-wg@xxxxxxxxxxx>
Date: Thursday, December 5, 2024 at 5:23
AM
To: The Sparkplug Working group <sparkplug-wg@xxxxxxxxxxx>
Cc: Kevin Kilroy <kevkilroy@xxxxxxxxx>
Subject: [sparkplug-wg] Unified Namespace

Hi,

 

Is SparkplugB a good framework for building a unified namespace?

 

The concern I have is around DDATA messages being sent with QoS 0. We have distributed sites that need to publish to a central broker over the public internet and I’m concerned messages would be lost en route.

 

I’m aware of the primary application but surely that would need to be hosted close to the EoN on a reliable local network?

 

Any advice or thoughts would be appreciated.

 

Thank you,

 

Kevin.


Back to the top