The more I build out the different pieces of aerogear.js, I realize that giving access to and promoting the use of direct options for jQuery.ajax defeats the purpose of the abstraction. The user could just use jQuery.ajax. I think to simplify the APIs, I am going to remove the access to those options and just provide the specific options I think would be useful for the user to have access to. Any thoughts or objections?

_______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

I assume only jQuery.ajax will be "blocked", the rest of jQuery would still be available, right? For instance, the normal $ usage to reference DOM element and attach an event/script is still available. On Sep 20, 2012, at 1:25 PM, Matthias Wessendorf wrote: > On Thu, Sep 20, 2012 at 7:19 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >> The more I build out the different pieces of aerogear.js, I realize that giving access to and promoting the use of direct options for jQuery.ajax defeats the purpose of the abstraction. The user could just use jQuery.ajax. I think to simplify the APIs, I am going to remove the access to those options and just provide the specific options I think would be useful for the user to have access to. >> >> Any thoughts or objections? > > +1 > > >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev