{"action":"created","issue":{"url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/251","repository_url":"https://api.github.com/repos/wamp-proto/wamp-proto","labels_url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/251/labels{/name}","comments_url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/251/comments","events_url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/251/events","html_url":"https://github.com/wamp-proto/wamp-proto/issues/251","id":168561914,"number":251,"title":"WAMP libraries are slightly different-can WAMP spec help?","user":{"login":"bradws","id":9676439,"avatar_url":"https://avatars.githubusercontent.com/u/9676439?v=3","gravatar_id":"","url":"https://api.github.com/users/bradws","html_url":"https://github.com/bradws","followers_url":"https://api.github.com/users/bradws/followers","following_url":"https://api.github.com/users/bradws/following{/other_user}","gists_url":"https://api.github.com/users/bradws/gists{/gist_id}","starred_url":"https://api.github.com/users/bradws/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bradws/subscriptions","organizations_url":"https://api.github.com/users/bradws/orgs","repos_url":"https://api.github.com/users/bradws/repos","events_url":"https://api.github.com/users/bradws/events{/privacy}","received_events_url":"https://api.github.com/users/bradws/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-08-01T03:58:46Z","updated_at":"2016-08-05T05:28:16Z","closed_at":null,"body":"Hi!\r\n\r\nMy issue may not be directly related to the 'specification' as such, however I believe this to be a valid point and probably worth discussing.\r\n\r\nI acknowledge that this is probably more to do with the implementation and specifics of WAMP libraries currently available.\r\n\r\nIn the spirit and goals of WAMP, and as an applications programmer, I noticed there is a slight (annoying) discrepancy of the WAMP libraries. For example, a person running an app using [AutobahnJS ](http://autobahn.ws/js/) cannot communicate _easily_ with another, say [Wampy](https://github.com/KSDaemon/wampy.js/) , or [WampSharp](https://github.com/Code-Sharp/WampSharp).\r\n\r\nAn example that immediately comes to mind is the standard RPC call. AutobahnJS returns it's results with a function thus:\r\n\r\n```\r\n// AutobahnJS\r\nvar add2 = function(args) {\r\n      return args[0] + args[1];\r\n};\r\n\r\nsession.register('com.myapp.add2', add2);\r\n```\r\n\r\n...however [Wampy](https://github.com/KSDaemon/wampy.js/) does it something like:\r\n\r\n```\r\n// Wampy\r\npublic add2( args ): any {\r\n    return[ {},  args[0] + args[1] ];  //  result returned as array index [1]\r\n}\r\nsession.register( \"com.myapp.add2\", add2 );\r\n```\r\n\r\nWriting apps handling these different scenarios is verbose. This requires re-writes, multiple code bases, etc.\r\n\r\nCan/does WAMPY have anything to say for the ordering of parameters?\r\n\r\nIn my experience and use cases, passing around and returning data has always really been a single object (e.g. a 'Client' object) with the related data being contained in the sub field or sub objects.\r\n\r\nCheers,\r\nbradws.\r\n"},"comment":{"url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/comments/237758592","html_url":"https://github.com/wamp-proto/wamp-proto/issues/251#issuecomment-237758592","issue_url":"https://api.github.com/repos/wamp-proto/wamp-proto/issues/251","id":237758592,"user":{"login":"konsultaner","id":2699538,"avatar_url":"https://avatars.githubusercontent.com/u/2699538?v=3","gravatar_id":"","url":"https://api.github.com/users/konsultaner","html_url":"https://github.com/konsultaner","followers_url":"https://api.github.com/users/konsultaner/followers","following_url":"https://api.github.com/users/konsultaner/following{/other_user}","gists_url":"https://api.github.com/users/konsultaner/gists{/gist_id}","starred_url":"https://api.github.com/users/konsultaner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/konsultaner/subscriptions","organizations_url":"https://api.github.com/users/konsultaner/orgs","repos_url":"https://api.github.com/users/konsultaner/repos","events_url":"https://api.github.com/users/konsultaner/events{/privacy}","received_events_url":"https://api.github.com/users/konsultaner/received_events","type":"User","site_admin":false},"created_at":"2016-08-05T05:28:16Z","updated_at":"2016-08-05T05:28:16Z","body":"I totally have to admit to @oberstet. I implemented the wamp protocol as router and client. We had some discusions about some protocol specific definitions. This was more then enough to figure out. If the protocol tells you how to design your access to the protocol is too much and also impossible. Most languages have their flavors and styles. It is not the job of a protocol definition to decide how to implement it."}}
{"actor":{"display_login":"konsultaner"}}