For a long time I've had to use IPv4 mapped addresses, because without them Mozilla tries to use the IPv6 socket for IPv4 communication, and ends up failing. (This was the case last month, I've not yet attempted disabling them again.) I supposed I should go look through the handful of bugs on bugzilla that have been marked FIXED and find the one that actually isn't...

'Do you want to risk security flaws?' is never going to go down well as a popup, or a pref...

Did anyone ever test this under RH9, or any of the other things in that bug on stuff hanging on shutdwn?

hey bradley! why would RH9 be any different? if your nameserver is slow to respond then the application will have to wait... and if the UI thread is waiting on gethostbyname, then the UI will hang.

RH9 uses NTPL, so gethostbyname is a cancelation point, and can be interupted with pthread_ when we want to quit. In theory, anyway. See the bug for more info. that was before I had RH9, though, and I still haven't tested.

is mozilla's DNS code the reason I keep getting "such-and-such.com could not be found" errors? I don't get the problem with other programs.

flubber dubber eat more rubber.

bbaetz: problem is we need a solution that works on Windows and other platforms. Windows does not support any notion of cancelation points. All you can do is terminate a thread :-(

Darin: Sure, but that what we want on unix too. The unix issue is that we can't terminate teh thread because its blocked, and doesn't go to see whats happening until later. I assume that thats not an issue on windows.

Bradley: i should just post the prototype somewhere ;-) ... each DNS thread just holds a strong reference back to an object which contains the global mutex for DNS (among other things). when threads complete, they consult this object to process the result of getaddrinfo. this object may be in the shutdown state, in which case the DNS thread will exit. so if we're on an operating system that allows child-threads to continue running after the main thread has exited (e.g., linux), then the "process" will not end until each thread discovers that it should shutdown. however, the main thread will be able to shutdown immediately, and i've noticed that this is enough to make the OS think the application is finished. e.g., i get back a bash prompt once the main thread completes even though there are still child threads active. now, i haven't tested thoroughly against the new linuxthreads impl in RH9... i should verify that i'm not depending on some side-effect of the old threads impl :-/

"a function like getaddrinfo or gethostbyname may block the calling thread seemingly forever"

Do you mean "so long users get impatient" or "hangs program?"

Each DNS query by a resolver does have retry and timeout limits, although poorly configured resolvers w/ bad server configs can take a really long time.

You Must Promise. To call your mother, to help old ladies cross the road, and to turn your cell phone off at the movies.

Whether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.

Adhere to Layout Guidelines. Did you leave 12 pixels between your push buttons? Does the positioning of your pop-up menus make sense, and when do you use a pop-up versus a scrolling list? Are you using the right types of buttons for the proper functions?

So far in these articles, I have only dipped a toe or two into Aqua's pool. I have covered basic aspects of building an Aqua-compliant application, including the building of photo-illustrative/3D application icons. Now it's time to address other components of our Mac OS X application.

Not quite as entertaining as Shrek, but Dock animation can be an important and useful function in your application. For example, Dock animation is a helpful way to indicate the status of your application.

In building your amazing Aqua application, one of the most important things to consider is the Dock. There are three things your app needs to be "Dock Compliant." Now, I write this knowing that the Dock will be going through some major changes soon, but for the most part, these should still hold true.

Adhere to Layout Guidelines. Did you leave 12 pixels between your push buttons? Does the positioning of your pop-up menus make sense, and when do you use a pop-up versus a scrolling list? Are you using the right types of buttons for the proper functions?

Adopt Sheets. I really like the use of Sheets in OS X. The use of Sheets lets me know which window my dialogue belongs to without hijacking my system.

To help you become a good Aqua citizen, Apple has created a few guidelines. I've put together a brief overview of them, and we'll be tackling many of them in the months to come.

Whether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.

My friend told me about your web site and I really enjoyed it. Very nicely done. Very interesting!

オンラインカジノ

WOW!!!! This is a great website.

business money