> I guess you mean confusing WAMP (as in "Web Application Messaging
> Protocol") with WAMP (as in "Windows Apache MySQL PHP").
>
> Indeed. It has always been confusing really.
> Besides, "web application" is a bit simplistic. Afterall, can't we use
> the protocol outside web application anyway? Do ypu mean web as in world
> wide web or as HTTP?
The "Web" in WAMP isn't covering all uses of WAMP any longer.
E.g. you can use WAMP with a Internet of Things app where there isn't
any "Web" involved at all.
In fact, the "W" formerly stood for "WebSocket", but that wasn't any
longer precise also (since WAMP can run over non-WebSocket as well).
Technically, what the protocol really provides is this:
Unified Application Messaging
That RPC+PubSub story.
However, "Unified Application Messaging Protocol (UAMP)" is bad also.
> >
> > It confuses everybody and make it so hard to google for it.
> >
>
> In retrospect, chosing "WAMP" as an acronym was a mistake. No doubt.
> I agree that discoverability and confusion _is_ a problem.
>
> Not just that... it's not "sexy". It's a bit sad, but you need to be
> easy to pronounce.
Yep. What would be good examples of names in the protocol field?
SPDY ("Speedy") seems nice ..
>
>
> > Go went for Golang.
> >
> > Rust went for rustlang.
> >
> > Can we settle for something like WAMP.ws (even if it's not just
> > websocket, it the main transport anyway) and put it everywhere ?
>
> Now, what should be do?
>
>
>
> Change it entirely. Don't go the Zope way by keeping a loaded name.
Alright. Bite the bullet. I'd be ready for this also.
However, this time, I guess we (the WAMP community) should reach
consensus on this.
We did the version 1 => 2 change which caused ripples for
implementors/users.
If we change the name, it'll be more ripples. I'm a little concerned
that this spills anger.
But it's probably now or never (rgd name change) ..
> Is there an animal that could somehow represent what WAMP is all about?
> Just a thought...
The "dual nature" of WAMP .. providing 2 things in 1.
Amphibia?
It can swim _and_ walk. (like in: it can do RPC _and_ PubSub).
I'm not particular good at this "naming game" ..
The other source of inspiration might be: WAMP provides an application
communication _fabric_.
Mmh.
/Tobias