Skip to content

An illogical requestID #5

@minyoung90

Description

@minyoung90

In latest VTN and VEN, for examples,

<?xml version="1.0" encoding="utf-8"?><oadrPayload xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://openadr.org/oadr-2.0b/2012/07">  <oadrSignedObject>    <oadrRequestEvent d3p1:schemaVersion="2.0b" xmlns:d3p1="http://docs.oasis-open.org/ns/energyinterop/201110">      <eiRequestEvent xmlns="http://docs.oasis-open.org/ns/energyinterop/201110/payloads">        <requestID>032ab6bb5b</requestID>        <d3p1:venID>7e8a2bd6e5127399da05</d3p1:venID>      </eiRequestEvent>    </oadrRequestEvent>  </oadrSignedObject></oadrPayload>

<?xml version="1.0" encoding="utf-8"?><oadrPayload xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://openadr.org/oadr-2.0b/2012/07">  <oadrSignedObject>    <oadrDistributeEvent d3p1:schemaVersion="2.0b" xmlns:d3p1="http://docs.oasis-open.org/ns/energyinterop/201110">      <d3p1:eiResponse>        <d3p1:responseCode>200</d3p1:responseCode>        <d3p1:responseDescription>OK</d3p1:responseDescription>        <requestID xmlns="http://docs.oasis-open.org/ns/energyinterop/201110/payloads">470b8d3324d1f3c635db</requestID>      </d3p1:eiResponse>      <requestID xmlns="http://docs.oasis-open.org/ns/energyinterop/201110/payloads">df970668ffb36058ba06</requestID>      <d3p1:vtnID>EPRI_VTN</d3p1:vtnID>    </oadrDistributeEvent>  </oadrSignedObject></oadrPayload>

Here are request requestID, 032ab6bb5b, from 'oadrRequestEvent'. and then reponse requestID, 470b8d3324d1f3c635db, from 'oadrDistributeEvent'I think above payloads are bounded in one transaction but requset and response's requestID(transaction ID) are different.Is it legal to act like above in OpenADR 2.0b standard specification?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions