[cosmo-dev] Re: [commits-cosmo] (travis) [6251] Bug 11373: remove remaining synchronous xhrs.

[Matthew Eernisse]

Travis,

All of the stuff you did looks good -- although I did notice the calls 
for loading items for both cal and list view are still synchronous.

Since those are probably the source of the biggest wait times (after the 
big ol' cooked dojo.js file), and the usual source of errors that 
prevent the UI from finishing rendering, was there some reason you 
didn't convert those to async calls? Or were you planning to do this 
later on?

Even with your changes, if there's a problem now with one of those two 
calls, or they're just super-slow, you'll still be looking at the 
"Loading the app..." message, and no UI. I thought that's what we were 
trying to fix with all these changes.

Do we need to do some work in that area (i.e., making those calls async, 
but the UI seem to block)? Users eventualy need to be able to load the 
UI with no collections and no data, anyway, so we'll be touching that 
code anyhow.

Also, is there somewhere where you've documented what 
cosmo.service.tickler.wrapService is for, or what exactly it does?

There are no comments of any kind in the module, but it's what's 
returning the object that getDashboardItems/getItems is being called on. 
I was trying to see where those sync values of true were getting passed 
along to (I figured an io.bind call), and couldn't really figure out 
what the tickler part of that code was doing.

Thanks.


Matthew