Bug while changing transports
ptejada opened this issue · comments
Ok so i've been developing a few little demos to showcase the use of APE. While testing i had different apps using different transports. If i first navigate to a demo that uses websockets it will connect to APE for the first time and create the session. Then if i navigate to another demo which uses long-poling and the same session, the response of the very first request will have a few extra bits/characters which breaks the JSON parsing process. Below is a screenshot of firebug
It might not be relevant since in a production environment you will most likely want to be consistent with the transport of choice.