Hello, Jeff! ??>> I'm doing it under Mozilla Thunderbird 1.5.0.10. If there are errors ??>> in my code, please, point them.
JW> So, first, you should really check return codes for success or failure, JW> and you should null-check your do_QueryInterfaces in case the object JW> doesn't implement that interface. Without those checks it's easy to JW> have crashes or incorrect behavior if something goes wrong or an object JW> doesn't implement the interfaces you thought it implemented. The code I actually use a bit more complex, than I provided here. There I do all checks for nsresult returned, but here is a sample of steps I use. ??>> After AsyncOpen modal dialog is displayed, which waits for HTTP ??>> transaction end. JW> So, it seems possible that these callbacks occur on the same thread on JW> which AsyncOpen is called (this is how it's always occurred for me, and JW> the existence of an nsIRequestObserverProxy interface suggests this is JW> policy -- it really should be documented in the IDL if true). If you JW> open the modal dialog from the same thread as the channel is opened, JW> you'd never get the listener notifications (notification callbacks may JW> have a different policy). What happens if you don't open the modal JW> dialog? Do you get request observer notifications? The actual problem here is using "POST" http method. If, for the same code, I comment out "POST" data, and use simply "GET" method, all notifications are sent, and everything is ok. I have a debug log for these two methods, and now I'm going to check it. I can post is here, but I have some doubts, because it is rather latge. Alexey Ousov _______________________________________________ dev-tech-network mailing list [EMAIL PROTECTED] https://lists.mozilla.org/listinfo/dev-tech-network
