5 ms·
WAMP – The Web Application Messaging Protocol
- specialist 11y agoI'm unclear why the root node of WAMP messages is a JSON Array. The rationalization for verbose, weird, ambiguous formats like XML and JSON is that they're "self-describing". Might as well just use MSGPACK or something.
- oberstet 11y agoWAMP can use different serialization formats, and MsgPack is one of them.
- liviu 11y agoI'm using deepstream.io for a project and it works well so far. It has some extra features like distribuited RPC calls, realtime search provider and transforming outgoing data.
- theknarf 11y agoWAMP usually means the "Windows, Apache, MySQL, PHP" stack. So creating a new "web technology" with the same abbreviation is a bit stupid. Your going to have a bad time getting search working.
- mhurron 11y ago> WAMP usually means the "Windows, Apache, MySQL, PHP" stack Ya, but no one in their right mind runs that.
- cbd1984 11y agoAll the more reason to avoid the acronym, then; the people who are stuck with it need all the help they can get.
- cbd1984 11y ago> WAMP usually means the "Windows, Apache, MySQL, PHP" stack. The solution is simple: Wait for everyone to replace MySQL with its non-Oracle clone, MariaDB. See? Easy! Or maybe they'll go the NoSQL route and use MongoDB.
- unwind 11y agoA quick test searching for "WAMP protocol" works just fine (wamp.ws is the #1 result) and isn't too hard to type. Without "protocol" the OP site drops to #4. I did not log out of the Google mothership so perhaps my results are skewed, but I also haven't heard of the WAMP protocol before. :)
- Rifu 11y agoThough I do agree with the general sentiment of your comment, I should point out that the maintainers of this project do address this issue in their FAQ[0]. [0] http://wamp.ws/faq/#naming http://wamp.ws/faq/#naming
- urda 11y ago> Because of this potential ambiguity, here is what we recommend for authors/implementors Potential ambiguity? It's nothing but ambiguity! What were they thinking.
- degenerate 11y agoWow. You can't just... use the same acronym and assume everything is hunky dory because you pronounce it differently. It's still the same damn letters! This project should have gone with "WebMP" or the full WAMPWS acronym. By "stealing" an existing, long-running and popular acronym, the maintainers are going to stifle this project no matter how much they try to separate themselves from WAMP. Trick question: is it possible to run WAMP on WAMP?
- sumedh 11y agoYou know when you have to create a separate section just to explain your name that is the time you realize maybe this was not such a good idea.
- jrslv 11y agoGood point, however I wouldn't consider this stack (Windows, Apache, MySQL and PHP) a huge rival for future in terms of growing number of search engine results.
- powertower 11y agoWAMP has been a thing since 2003, with over 12 years of history. It is the predominant Windows PHP development environment and Apache stack - that has millions of users worldwide.
- pluma 11y agoMaybe not in the startup world, but because of the popularity of LAMP and the ubiquity of Windows, a lot of people use WAMP (e.g. via XAMPP) as a local development stack. It's important to be aware of our own cognitive biases: while Linux is the de-facto standard on the server side and the startup scene is dominated by MBPs and its variants (with a good helping of Linux again, though often in VMs), this only represents a tiny fraction of developers. Dark Matter Developers are a thing.
- RaitoBezarius 11y agoWhile WAMP is awesome on the paper. (And it is definitely awesome.) Some disclaimer would be fair. Currently, the most complete router implementation is Crossbar.io (Python), while it is functional, documentation is lacking cruelly. For example, we don't know yet how to do proper cookie authentication. Or the WAMP-CRA authentication has a little flaw and should be replaced with a new auth scheme. Another example is that AutobahnPython or AutobahnJS are lacking documentation on CallOptions or SubscribeOptions and other things. There is a lot of boilerplate to achieve simple things like... managing a connection lifetime (there is onopen, onclose, and onclose gives you some details, but no consistent, it's hard to know when auth failed or connection aborted). Anyway. It just means that WAMP is in his debuts, I hate some weaknesses of the WAMP ecosystem (documentation, boilerplate, etc...) Nevertheless, it's awesome and you should definitely try something with. And if you can, contribute and make it incredible. (No offense, I'm a fond of WAMP, but I don't want people to say things that are obvious like: "oh there is no doc it's a shitty project" -- WAMP is moving fast. Very fast.)
- k__ 11y agoSo this is an alternative to hook.io?
- deleted 11y ago[deleted]
- thirdknife 11y agoand also socket.io?
- oberstet 11y agosocket.io is a JS point solution for PubSub only .. http://wamp.ws/compared/#socketio http://wamp.ws/compared/#socketio
- oberstet 11y agoIn a way yes, but WAMP offer more functionality (e.g. PubSub)
- johnbellone 11y agoI read this as "Winamp" and I had a flood of nostalgia. The good ole' days.
- degenerate 11y agoIt really whips the llama's ass!
- nkg 11y agoI read this as "WAMP" and I had a flood of bad memories.
- BillinghamJ 11y agoMight have misinterpreted this, but from reading all the slides - it seems that even for RPC, you have to pass all messages via a central server. For use internally between services, this seems like a really bad idea. Seems like it'd be a big bottleneck when it came to scaling.
- luhn 11y agoNo, you're right. Multi-node support is on the roadmap, but no ETA yet. Until that's implemented I can't seriously consider it for production. I love the concept, though. One unified layered for all your services.
- breakingcups 11y agoI've been forced to use this on a contracting-job and not exactly happy with the state of the current components. It's a bit too brittle, there's usually little to no documentation on the different authmethods between different components (MDWamp and AutobahnJS specifically). There's sloppy typo's and every few hours the server decides not to accept connections for a certain auth-id anymore until it is rebooted.
- oberstet 11y agoRegarding docs, yes agreed. But we are working on this and things are improving. This is still moving fast . Rgd the server stability issues you mention: what WAMP router are you using?
- fenesiistvan 11y agoCan somebody elaborate why the need for such libraries, when: -client side websocket handling is ~3 lines of code -server side websocket is ~200 lines of code even with pure bit level C/C++ on top of any TCP socket (the websocket RFC is very simple) -writing a simple protocol for yourself is obvious So, you can write all these for yourself within one day and then you know all the details. It takes more time to study how to use others code and you will still remain on the wrong path if some modification would be needed, feature missing or you have to fix a bug.
- oberstet 11y agoMinor, but still: you can't write a conforming WebSocket client in 3 lines of code, and you can't write a conforming WebSocket server in 200 lines of code. I know: I have written a couple. Anyway. Moot, since this isn't about WebSocket. WebSocket only provides you with a bidirectional message channel. It's low-level, and does not provide application messaging. WAMP can run _over_ WebSocket, but also other message channels. E.g. you can have WAMP running over a shared-memory message queue.
- fenesiistvan 11y agoMaybe web developers are not comfortable with the basics?
- wolframhempel 11y agoMore complex realtime applications can benefit from higher level concepts like data-sync (observable objects that share state between clients), e.g. http://deepstream.io/ http://deepstream.io/ or https://www.firebase.com/ https://www.firebase.com/ or more complex routing strategies, e.g. AMQP exchanges. A great example of the impact of this kind of standardized protocol / architecture on top of a low level protocol would be REST on top of HTTP
- fenesiistvan 11y agoOk, but then why the focus on the "websocket" which is just a simple protocol over TCP. Why not an "universal" app server which can handle also other transport layers. We already have these kind of frameworks (and "websocket" is just a single line on their endless feature list) Edit: anyway, i see where this module would fit, i was just curious why we need to use for everything a foreign component and create more dependencies for our projects instead of developing in-house such trivial modules