<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>i've started to add jsonp support to aerogear.js pipeline and i wanted to get some feedback that i'm on the right track</div><div><br></div><div>i have a example project here : <a href="https://github.com/lholmquist/WoWAerogear">https://github.com/lholmquist/WoWAerogear</a></div><div><br></div><div>those of you with yeoman installed can type "yeoman build" then "yeoman server", you might be able to get away with just the second command.</div><div><br></div><div>There are 2 requests, the first using jQuery, so i had a baseline, and the second is with a modified version of aerogear.js</div><div><br></div><div><div>pipeline.add( {</div><div> …….</div><div> settings: {</div><div> ………...</div><div> jsonp: true,</div><div> callback: "myCallback"</div><div> }</div><div> } );</div></div><div><br></div><div>I think declaring it during the creation makes sense. </div><div>Being able to override the jsonpCallback would add a layer of security for when the server defines the callback, I not sure if this should be put into a jsonpSettings:{ } or leave it were it is</div><div><br></div><div><br></div><div>i only tested read atm, just wanted to get some feedback first</div><div><br></div><div><br></div><div>-Luke</div></body></html>