So much of AJAX is making a polling protocol (HTTP) look like a push protocol. What really needs to happen is that browsers and the "web" need to adopt a push protocol like XMPP Publish-Subscribe http://www.xmpp.org/extensions/xep-0060.html to augment HTTP.
The suite never died. It was decided back in early "Phoenix" days to switch priorities, but Firefox and SeaMonkey have still been arm and arm. Most features that make it into Firefox are developed in SeaMonkey. Firefox is simply lighter weight and more aimed at the "grandmother can use this" style UI.
It pulls up a window on the machine you're on, and shows your X session (browser, word processor) and you use the keyboard, mouse, internet connetion, and monitor of the host machine. You work on your document for awhile, unplug.... go to a different machine, and your word processor is right where you left it. You keep working on your document, all powered by the USB port. There's no evidence on the host machine of what you were running or what you did.
This simply makes it so that bug patches don't get stepped on all of the time. Developers that are submitting feature updates will have to simply time their submittion. I don't think it'll slow development at all, it'll just polish releases more easily.
I tend to do a lot of customization for daemons like a Apache, and some libraries like PHP. However, it's best to leave most libraries to your packaging system being as many other packages are likely to depend on them.
It's a balance. Compile when you want/need to... but try to limit it to major apps like daemons that not many other packages depend on.
I doubt the rumor is true. Doesn't anyone remember how they squashed UO2? Why would they remake the game from scratch instead of just using what they already had? I don't understand why they would use an Unreal engine.
As I scan through, I see several posts of people giving up hope, and even those showing signs of dispair because they have an ssh server that they don't want to remove that service from. Fear not my friends.
Simply download the rpms (openssh, openssh-askpass, openssh-clients, openssh-server) and give it an old
rpm -iU openssh, openssh-askpass, openssh-clients, openssh-server
It'll update everyting for you/and/ restart your services real quick.
Or, if you feel like being a man, you can compile the sucker, and copy over the older versions and restart the services manually.
Either way, there is no need to dispair. You're not going to lose your ability to serve ssh securely to your users. Of course, this comes as no news to most of you, but just wanted to explain it to the people who didn't seem to understand.
Slashdot Mirror
So much of AJAX is making a polling protocol (HTTP) look like a push protocol. What really needs to happen is that browsers and the "web" need to adopt a push protocol like XMPP Publish-Subscribe http://www.xmpp.org/extensions/xep-0060.html to augment HTTP.
The suite never died. It was decided back in early "Phoenix" days to switch priorities, but Firefox and SeaMonkey have still been arm and arm. Most features that make it into Firefox are developed in SeaMonkey. Firefox is simply lighter weight and more aimed at the "grandmother can use this" style UI.
Psi, one of the most popular Jabber clients out there has announced that they are working on support for jingle. http://psi-im.org/forum/post/24491
It pulls up a window on the machine you're on, and shows your X session (browser, word processor) and you use the keyboard, mouse, internet connetion, and monitor of the host machine. You work on your document for awhile, unplug.... go to a different machine, and your word processor is right where you left it. You keep working on your document, all powered by the USB port. There's no evidence on the host machine of what you were running or what you did.
This simply makes it so that bug patches don't get stepped on all of the time. Developers that are submitting feature updates will have to simply time their submittion. I don't think it'll slow development at all, it'll just polish releases more easily.
I tend to do a lot of customization for daemons like a Apache, and some libraries like PHP. However, it's best to leave most libraries to your packaging system being as many other packages are likely to depend on them. It's a balance. Compile when you want/need to... but try to limit it to major apps like daemons that not many other packages depend on.
I doubt the rumor is true. Doesn't anyone remember how they squashed UO2? Why would they remake the game from scratch instead of just using what they already had? I don't understand why they would use an Unreal engine.
As I scan through, I see several posts of people giving up hope, and even those showing signs of dispair because they have an ssh server that they don't want to remove that service from. Fear not my friends. Simply download the rpms (openssh, openssh-askpass, openssh-clients, openssh-server) and give it an old rpm -iU openssh, openssh-askpass, openssh-clients, openssh-server It'll update everyting for you /and/ restart your services real quick.
Or, if you feel like being a man, you can compile the sucker, and copy over the older versions and restart the services manually.
Either way, there is no need to dispair. You're not going to lose your ability to serve ssh securely to your users. Of course, this comes as no news to most of you, but just wanted to explain it to the people who didn't seem to understand.