I wouldn't actually blame Microsoft for it. They are trying quite hard lately, and it's going to be standard in their new OS. Heck, even their new filesharing tool (3degrees) _IS_ IPv6 ONLY.
I think you should rather blame some other company - Cisco. Had they delivered production quality IPv6 IOS much earlier, I believe ipv6 deployment would be somewhere else. They finally managed to deliver somewhat useable IOS image early this year. Yes, clients are important, but without reliable blackbone, they're useless.
Well, as an IRCnet ircd developer, i believe (as do EFnet/undernet coders), that making thread/user is really not the way to go (since IRC has to keep global state - therefore you need to lock here and there and in the result you waste more resources on locking than you'd think the benefit of threaded ircd is).
JV
Unfortunately irc daemon can't be threaded in that way (you'd waste quit some time on locking). But yes, i think ircd is one of the few daemons which are almost 'pushing ip stack' to the limits - after all, having 40000 (twisted*.dal.net) connections in one process ain't that bad.
Seems the poster doesn't know IRC history.
First IRC server on the world, has been obviously tolsun.oulu.fi. This server is *still* running as part of IRCnet (The other side of The Great Split).
Saying "Oldest server on EFnet going offline" is correct "oldest in world" isn't.
JV
Slashdot Mirror
I wouldn't actually blame Microsoft for it. They are trying quite hard lately, and it's going to be standard in their new OS. Heck, even their new filesharing tool (3degrees) _IS_ IPv6 ONLY.
I think you should rather blame some other company - Cisco. Had they delivered production quality IPv6 IOS much earlier, I believe ipv6 deployment would be somewhere else. They finally managed to deliver somewhat useable IOS image early this year. Yes, clients are important, but without reliable blackbone, they're useless.
Samba can be configured that filenames are insensitive (which is default since samba 2.2)
Well, as an IRCnet ircd developer, i believe (as do EFnet/undernet coders), that making thread/user is really not the way to go (since IRC has to keep global state - therefore you need to lock here and there and in the result you waste more resources on locking than you'd think the benefit of threaded ircd is). JV
Unfortunately irc daemon can't be threaded in that way (you'd waste quit some time on locking). But yes, i think ircd is one of the few daemons which are almost 'pushing ip stack' to the limits - after all, having 40000 (twisted*.dal.net) connections in one process ain't that bad.
Seems the poster doesn't know IRC history.
First IRC server on the world, has been obviously tolsun.oulu.fi. This server is *still* running as part of IRCnet (The other side of The Great Split).
Saying "Oldest server on EFnet going offline" is correct "oldest in world" isn't.
JV