WAMP Specifications (Details/Options)

#1

I am a bit confused reading through the current WAMP specifications. In particular, the simple profile specification defines a HELLO message as:

[HELLO, Realm|uri, Details|dict]

It then refers to the details portion of the message as follows:

Hello.Details.*

This same semantic continues in the advanced profile specification but all of a sudden the following crops up:

HELLO.Options.*

So my question is, are “Details” and “Options” actually interchangeable terms or are they separate things? The examples seem to indicate that they are one and the same but I just wanted to make sure. For example:

[1, “realm1”,
{
“roles”: …,
“authmethods”: [“wampcra”],
“authid”: “peter”
}
]

``

Thanks,

Dave

0 Likes

#2

Hi David!

“Options” and “Details” are indeed used synonymously here - and really shouldn’t be. AFAIK, throughout the spec"options" should be used for a dictionary which can be sent as part of a call/publish/message which initiates a communication, while “details” is for dictionaries which are sent as part of results/events/messages which react to a previous communication.

We’ll try and clean things up in this regard.

Regards,

Alex

···

Am Dienstag, 13. Januar 2015 22:10:37 UTC+1 schrieb David Chappelle:

I am a bit confused reading through the current WAMP specifications. In particular, the simple profile specification defines a HELLO message as:

[HELLO, Realm|uri, Details|dict]

It then refers to the details portion of the message as follows:

Hello.Details.*

This same semantic continues in the advanced profile specification but all of a sudden the following crops up:

HELLO.Options.*

So my question is, are “Details” and “Options” actually interchangeable terms or are they separate things? The examples seem to indicate that they are one and the same but I just wanted to make sure. For example:

[1, “realm1”,
{
“roles”: …,
“authmethods”: [“wampcra”],
“authid”: “peter”
}
]

``

Thanks,

Dave

0 Likes

#3

Hi David!

"Options" and "Details" are indeed used synonymously here - and really
shouldn't be. AFAIK, throughout the spec"options" should be used for a

No. They are different things:

Options: is something a client requests the router to do
Details: is something the router provides to the client

dictionary which can be sent as part of a call/publish/message which
initiates a communication, while "details" is for dictionaries which are
sent as part of results/events/messages which react to a previous
communication.

We'll try and clean things up in this regard.

No: see above

···

Am 14.01.2015 um 11:35 schrieb Alexander Gödde:

Regards,

Alex

Am Dienstag, 13. Januar 2015 22:10:37 UTC+1 schrieb David Chappelle:

    I am a bit confused reading through the current WAMP specifications.
    In particular, the simple profile specification defines a HELLO
    message as:

         [HELLO, Realm|uri, Details|dict]

    It then refers to the details portion of the message as follows:

         Hello.Details.*

    This same semantic continues in the advanced profile specification
    but all of a sudden the following crops up:

         HELLO.Options.*

    So my question is, are "Details" and "Options" actually
    interchangeable terms or are they separate things? The examples seem
    to indicate that they are one and the same but I just wanted to make
    sure. For example:

    >
    [1,"realm1",
    {
    "roles":...,
    "authmethods":["wampcra"],
    "authid":"peter"
    }
    ]
    >

    Thanks,

    Dave

--
You received this message because you are subscribed to the Google
Groups "Autobahn" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to autobahnws+...@googlegroups.com
<mailto:autobahnws+...@googlegroups.com>.
To post to this group, send email to autob...@googlegroups.com
<mailto:autob...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/autobahnws/173d4a04-c863-4007-9971-d23d290f6fdb%40googlegroups.com
<https://groups.google.com/d/msgid/autobahnws/173d4a04-c863-4007-9971-d23d290f6fdb%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.

0 Likes

#4

So why is there Hello.Details in the basic profile specification and Hello.Options in the advanced profile specification? Seems contradictory.

···

On Wed, Jan 14, 2015 at 7:25 AM, Tobias Oberstein tobias.o...@gmail.com wrote:

Hi David!

“Options” and “Details” are indeed used synonymously here - and really

shouldn’t be. AFAIK, throughout the spec"options" should be used for a
dictionary which can be sent as part of a call/publish/message which

initiates a communication, while “details” is for dictionaries which are

sent as part of results/events/messages which react to a previous

communication.

We’ll try and clean things up in this regard.
Am 14.01.2015 um 11:35 schrieb Alexander Gödde:

No. They are different things:

Options: is something a client requests the router to do

Details: is something the router provides to the client

No: see above

Regards,

Alex

Am Dienstag, 13. Januar 2015 22:10:37 UTC+1 schrieb David Chappelle:

I am a bit confused reading through the current WAMP specifications.

In particular, the simple profile specification defines a HELLO

message as:



     [HELLO, Realm|uri, Details|dict]



It then refers to the details portion of the message as follows:



     Hello.Details.*



This same semantic continues in the advanced profile specification

but all of a sudden the following crops up:



     HELLO.Options.*



So my question is, are "Details" and "Options" actually

interchangeable terms or are they separate things? The examples seem

to indicate that they are one and the same but I just wanted to make

sure. For example:



|

[1,"realm1",

{

"roles":...,

"authmethods":["wampcra"],

"authid":"peter"

}

]

|



Thanks,



Dave

You received this message because you are subscribed to the Google

Groups “Autobahn” group.

To unsubscribe from this group and stop receiving emails from it, send

an email to autobahnws+unsubscribe@googlegroups.com

mailto:autobahnws+unsub...@googlegroups.com.

To post to this group, send email to autob...@googlegroups.com

mailto:autobahnws@googlegroups.com.

To view this discussion on the web visit

https://groups.google.com/d/msgid/autobahnws/173d4a04-c863-4007-9971-d23d290f6fdb%40googlegroups.com

<https://groups.google.com/d/msgid/autobahnws/173d4a04-c863-4007-9971-d23d290f6fdb%40googlegroups.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.

You received this message because you are subscribed to a topic in the Google Groups “Autobahn” group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/autobahnws/rdKf7wZF1QM/unsubscribe.

To unsubscribe from this group and all its topics, send an email to autobahnws+unsubscribe@googlegroups.com.

To post to this group, send email to autob...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/autobahnws/54B6603C.8040209%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

0 Likes