On Thu, Dec 17, 2015 at 12:56:54PM -0800, Kevin Carhart wrote:
> On Thu, 17 Dec 2015, Chris Brannon wrote:
> >Sorry for the rant
> 
> This is half the fun. :)

Indeed, and I'm glad to find I'm not the only one who thinks this.
Having to work with some fairly inaccessible web stuff at work (read anything
made by Atlassian from my experience)
and consequently spending more than too much time grapling with json APIs to
try and do simple things like move tasks to "in progress"
or check what development tasks I've got to do is a constant frustration.
Fortunately some of these APIs have been scripted by other people,
but it'd be really nice if there was some kind of standard which wasn't "use
the crazy, ever evolving, UI which we force on you".

> Seriously, I have a fastmail account also, so I will pull this up now and
> find out what happens.  I think all roads lead to xhr.  I would be willing
> to bet that fastmail uses it.  BUT-- it's true, there may be something more
> easy that will help.

I don't personally have an account but,
since I've ended up with more time than I expected,
I'm beginning to think that getting a somewhat functional XHR object is more
pressing than a js engine switch.
As such, are there any incremental steps we can take which will get us at least
a basic XHR object which don't require rewriting (or duplicating using an async
design) Edbrowse's comms layer?

Cheers,
Adam.