[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ENERGYINTEROP-692) Support Pub/Sub as well as SOA
[ https://issues.oasis-open.org/browse/ENERGYINTEROP-692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=80648#comment-80648 ]
William Cox commented on ENERGYINTEROP-692:
-------------------------------------------
Line apparently misread.
CTS is agnostic on how the message payloads are exchanged.
TC editor discussion on deriving actor and facet from cloud-native computing practices (and relating to Actor Architecture). See TC email.
> Support Pub/Sub as well as SOA
> ------------------------------
>
> Key: ENERGYINTEROP-692
> URL: https://issues.oasis-open.org/browse/ENERGYINTEROP-692
> Project: OASIS Energy Interoperation TC
> Issue Type: Bug
> Components: cts
> Affects Versions: CTSPR01
> Environment: Rolando Herrero https://lists.oasis-open.org/archives/energyinterop-comment/202111/msg00003.html
> Reporter: Toby Considine
> Assignee: William Cox
> Priority: Major
> Labels: ARCH-CONF, CLARITY
>
> Page: 16, Line: 267-269 -> Message transport is affected by the topology. SOA is typically client/server while many of the modern IoT topologies are publish/subscribe (relying on MQTT or AMQP session management). This document should take into account the support of this latter scenario.
--
This message was sent by Atlassian Jira
(v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]