While I am developing on Firefox today I tested and fixed some issues under Chromium (webkit based), Opera (opera based) and Konquorer (khtml based). My pub/sub demo worked the same in all four browsers (and at the same time I might add). We tried with IE8 on Luke’s machine but the error messages were cryptic. I’ll have to get my hands on a windows box at some point but I’m guessing the biggest issues are going to be trailing commas or keywords which are similar in the amqp spec and javascript (e.g. I ran into void and class keyword issues with the webkit browsers).
One thing to note is Chromium’s integrated debugger is a lot faster than Firebug. I haven’t used it extensively but if it can break at breakpoints and introspect objects without getting screwy I might end up switching. I really like firebug but lately it has become dog slow. It usually takes a couple of minutes of waiting for each frame of data to be processed and displayed while under Chromium with their debugger on, the slowdown is noticeable but not significant compared to when the debugger is off.
UPDATE: Chromium’s debugger is probably faster because it doesn’t actually do anything that I can see. It displays scripts but doesn’t actually break into the code
[read this post in: ar de es fr it ja ko pt ru zh-CN ]
Sticking my Apache hat on, we’d love to have this in Qpid.
I’d be happy to help with the paperwork side (it’s not particularly onerous).
- Aidan
Comment by Aidan Skinner — September 14, 2009 @ 4:34 pm
Hi Aidan,
I want to get it to a usable state before proposing it for the Apache Qpid project but I will be posting on the qpid mailing list sometime this week to get some feedback.
Comment by J5 — September 14, 2009 @ 4:48 pm
Sweet
Comment by Aidan Skinner — September 14, 2009 @ 5:44 pm