Hi guys, I'm beginning to look at porting GTDInbox for Gmail (http:// www.gtdinbox.com) to Chrome - a lot of our users are wanting to use Chrome!
The one major barrier holding us back is the inability to monitor HTTP requests. We absolutely rely on them to detect environment actions (e.g. thread label added/removed, new messages arrived, etc.) to keep our view of the user's data accurate. There's no other robust way for us to work with Gmail (we cannot bear to go back to DOM event monitoring!). Note that we don't need to modify the HTTP Requests. We just need read- only access to them, whereupon we do some string parsing to extract the events that they represent. (In fact, most event monitoring only requires the URL parameter of the request, although it would be more robust to be able to read the additional data as well). I think this is quite a generic requirement for anyone working with modern web apps, where the only way to stay up to date with state changes is to be able to watch those AJAX requests. This aside, I'm really looking forward to porting to Chrome - it all seems very clean and refreshingly straightforward :) Andy PS This is similar to the earlier http://groups.google.com/group/chromium-extensions/browse_thread/thread/fb8c1f28c4a63670 . But, it seems the main objection there was performance wrt to the ability to also write to the request stack. I'm hopeful that a simple read-only solution, perhaps as a first step, would not incur such a cost. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
