Most isp's cant be arsed to setup their routers correctly for mutlicast to work.
That and there are few lowbandwidth examples of multicast software, and none popular.
IRC seems to me a better fit with its channels and server model, cept what to use to retrieve the headers that youd miss when your offline.
SMTP and NNTP are both still a pull technologys for the last mile, and much higher latency then irc.
Push is easy to make.
Getting Push used is something that is very hard.
For the same reason why soap seems more popular then rpc, well have to wait a while for it.
People are just too happy piggybacking stuff onto http.
it seems a few peoples here dont get it.
RSS is the file format, not the transfer via HTTP
The whole pull problem is a problem with HTTP, in theory you could make an irc like protocol and transmit via that, solving some of the subscription, distribution and pull problems.
Its more intresting to find out what the forces are that make a MBA so valueable.
I think the effects of unrealisticly increasing short term profits for the shareholders is a mayor influence here, one that will start to fail, like the bubble but worse.
Its worse than that,
Because in their implementation java did share information on the server between connections and the php implementation did this less, the php version could be cloned over multiple servers.
They could have done the same with the java implementation.
Your number two i fix with cygwin, with the stability of w2k and cygwin tools such as an opensshd service, i often dont notice the difference between my linux and windows machine for the shell stuff.
There was this little serie called firefly that was just about what you described.
It did suffer under a need for continutity, but the flaws and humor were there.
Too bad its cancelled after the first 15 episodes.
Except that you only should disable the firewall if your having problem getting the updates.
Just like a few installs ask for the virus scanner to be turned off, only do it if the install fails and your sure its really not a virus.
Its all a support issue, they dont want people complaining about windowsupdate because they have a too tight firewall.
I guess java could do it, but there are enough big problems.
The jvm version installed is often to old, and updating costs too much bandwidth.
Rmi is arguably too difficult.
Swing is still missing a common guibuilder.
Swing is hard to remote via rmi.
Programming for a distributed enviroment isnt a skill most people have.
Latency might be too high for naive GUI forwarding solutions.
Bandwidth might be too low for sending whole documents or emailarchives.
Security gets more difficult to get right for more richer applications. (just wait for the apps that expect the client side to not get decompiled and have special requests crafted)
Ofcourse most is true for any such application.
Slashdot Mirror
Sounds like typical patents to me...
WHat happens to mono if sun, the owners of java, buys monos biggest sponsor Novell?
I allways have this: I get to download at maybe 40 to 100KB/s and when it finishes i upload to others at 400KB/s to 2MB/sec
Most readers do that allready. At the same time some servers that host feeds dont support them.
Most isp's cant be arsed to setup their routers correctly for mutlicast to work. That and there are few lowbandwidth examples of multicast software, and none popular.
IRC seems to me a better fit with its channels and server model, cept what to use to retrieve the headers that youd miss when your offline. SMTP and NNTP are both still a pull technologys for the last mile, and much higher latency then irc.
Push is easy to make. Getting Push used is something that is very hard. For the same reason why soap seems more popular then rpc, well have to wait a while for it. People are just too happy piggybacking stuff onto http.
it seems a few peoples here dont get it. RSS is the file format, not the transfer via HTTP The whole pull problem is a problem with HTTP, in theory you could make an irc like protocol and transmit via that, solving some of the subscription, distribution and pull problems.
'Freedom not to use it' ugh defence number 1 of a monopoly, and gpl has one in the Linux area.
That is what killed XFree86. Something i think is stupid, alltough its unhandy to attribute the stuff everywhere, its understandable and usable.
http://feedreader.sf.net Its currently not being developed anymore, but its still a client that just does its job.
Do you want them to OSS to win ? if that means youll have to find a job in something else then programming ?
Ive been doing some opensource project because i couldnt get a job to write it. I think this situation will get worse.
why the jobmarket has been so bad
Its more intresting to find out what the forces are that make a MBA so valueable. I think the effects of unrealisticly increasing short term profits for the shareholders is a mayor influence here, one that will start to fail, like the bubble but worse.
Its worse than that, Because in their implementation java did share information on the server between connections and the php implementation did this less, the php version could be cloned over multiple servers. They could have done the same with the java implementation.
Altough the GPL doesnt come with an NDA it does have some nasty effects. Expecially the gplv3 patent clause. Anyways use what the os is good for.
If i need a GUI-less system i would use a bsd flavor, but thats beside the point.
Thats hardly portable between unices, anyways, i was talking about what 'i' use a unix shell for on day to day basis.
Your number two i fix with cygwin, with the stability of w2k and cygwin tools such as an opensshd service, i often dont notice the difference between my linux and windows machine for the shell stuff.
There was this little serie called firefly that was just about what you described. It did suffer under a need for continutity, but the flaws and humor were there. Too bad its cancelled after the first 15 episodes.
Except that you only should disable the firewall if your having problem getting the updates. Just like a few installs ask for the virus scanner to be turned off, only do it if the install fails and your sure its really not a virus. Its all a support issue, they dont want people complaining about windowsupdate because they have a too tight firewall.
Debuging into system librarys ? Librarys should be blackboxes, and you should be able to trust them.
I guess java could do it, but there are enough big problems. The jvm version installed is often to old, and updating costs too much bandwidth. Rmi is arguably too difficult. Swing is still missing a common guibuilder. Swing is hard to remote via rmi. Programming for a distributed enviroment isnt a skill most people have. Latency might be too high for naive GUI forwarding solutions. Bandwidth might be too low for sending whole documents or emailarchives. Security gets more difficult to get right for more richer applications. (just wait for the apps that expect the client side to not get decompiled and have special requests crafted) Ofcourse most is true for any such application.
they probably just rip it to a half gig divx or something