{"action":"created","issue":{"url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/53","repository_url":"https://api.github.com/repos/shoreditch-ops/artillery-core","labels_url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/53/labels{/name}","comments_url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/53/comments","events_url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/53/events","html_url":"https://github.com/shoreditch-ops/artillery-core/issues/53","id":157012372,"number":53,"title":"Perform http & socket.io tasks in 1 flow","user":{"login":"ksplache","id":8825536,"avatar_url":"https://avatars.githubusercontent.com/u/8825536?v=3","gravatar_id":"","url":"https://api.github.com/users/ksplache","html_url":"https://github.com/ksplache","followers_url":"https://api.github.com/users/ksplache/followers","following_url":"https://api.github.com/users/ksplache/following{/other_user}","gists_url":"https://api.github.com/users/ksplache/gists{/gist_id}","starred_url":"https://api.github.com/users/ksplache/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ksplache/subscriptions","organizations_url":"https://api.github.com/users/ksplache/orgs","repos_url":"https://api.github.com/users/ksplache/repos","events_url":"https://api.github.com/users/ksplache/events{/privacy}","received_events_url":"https://api.github.com/users/ksplache/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-26T15:32:24Z","updated_at":"2016-05-26T15:56:50Z","closed_at":null,"body":"Web applications designed with both http and socket.io often have a sequence of events (i.e. a flow) that requires both http posts, gets, and socket.io calls.  Currently, you can have only one engine per flow so you cannot mix both http and socket.io within a flow.  Example:\r\n\r\n```\r\n  \"scenarios\": [\r\n    {\r\n      \"flow\": [\r\n        {\"post\": { \"url\": \"/somepost\", \"capture\": { \"json\": \"$.data\", \"as\": \"mydata\" } }},\r\n        {\"emit\": { \"channel\": \"echo\", \"data\": \"{{mydata}}\", \"response\": { \"channel\": \"echoed\" } }}\r\n        {\"think\": 1},\r\n      ]\r\n    }\r\n  ]\r\n```"},"comment":{"url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/comments/221914059","html_url":"https://github.com/shoreditch-ops/artillery-core/issues/53#issuecomment-221914059","issue_url":"https://api.github.com/repos/shoreditch-ops/artillery-core/issues/53","id":221914059,"user":{"login":"hassy","id":1490,"avatar_url":"https://avatars.githubusercontent.com/u/1490?v=3","gravatar_id":"","url":"https://api.github.com/users/hassy","html_url":"https://github.com/hassy","followers_url":"https://api.github.com/users/hassy/followers","following_url":"https://api.github.com/users/hassy/following{/other_user}","gists_url":"https://api.github.com/users/hassy/gists{/gist_id}","starred_url":"https://api.github.com/users/hassy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hassy/subscriptions","organizations_url":"https://api.github.com/users/hassy/orgs","repos_url":"https://api.github.com/users/hassy/repos","events_url":"https://api.github.com/users/hassy/events{/privacy}","received_events_url":"https://api.github.com/users/hassy/received_events","type":"User","site_admin":false},"created_at":"2016-05-26T15:56:50Z","updated_at":"2016-05-26T15:56:50Z","body":"Yes, go ahead, that sounds like a good approach for now 👍  Your engine will need to initialise a context to pass into the functions that will handle HTTP actions (see here: https://github.com/shoreditch-ops/artillery-core/blob/master/lib/engine_http.js#L242), but other than that I think it should be pretty straightforward.\r\n\r\nI had a think about being able to mix engines freely, but it would indeed be a significant change (maybe even too much to try to make work for any combination of engines)."}}
{"actor":{"display_login":"hassy"}}