In away this alternative already exists, https. If everyone starts serving their content from https servers how does filtering work? Since any rating information within the page is encrypted you have to decrypt the packets to see what is being sent. This is bad news for e-commerce, if packets are thrown away because they aren't understood or the encryption used is trivial, who is going to be happy about sending private info across the net?
What happens if sites are rated according to IP address, this then fails for virtual servers, multi user services etc.
Finally, in the event that they do this, what is to stop me designing and implementing my own protocol on top of TCP, UDP,... to transmit what ever information I want? Designing a reliable transmission protocol on top of UDP is really rather trivial.
No matter what it looks like, there isn't a.sig here.
Also, the larger that you make a cache, the more expensive a cache miss is (as you had to look through your cache to see that it wasn't there).
This depends on how you implement the cache, fully associative, set associative or what's the other one again?
Typically (memory) caches in PC's are set associative, therefore making the cache larger wouldn't have an adverse effect. Same number of sets, just a larger associative lookup for that set. All it means is more transistors -> more expensive. Even if you increase the number of sets there is no negative effect, since a cache calculates the area of cache to be checked using the memory address.
Overall, a cache will complete it's lookup in one clock cycle no matter how large it is.
No matter what it looks like, there isn't a.sig here.
The original [British] government bill on electronic commerce required a third party to hold a key for any encrypted message - ie key escrow. I recall a certain large software company strongly endorsing the proposals...
No matter what it looks like, there isn't a.sig here.
Nah! Nah! Read it before it got posted here:) I found it really rather funny. I'd love to see this made into an episode, maybe one that gets a web broadcast, that'd be really cool!
On that topic: surely this could actually done by the web browser rather than a distributed client. If you have a page online you're bound to check it yourself to make sure it's OK. With an appropriate browser or plugin your page could then be indexed and submitted to a search engine. And then once you start surfing any page you visit could be automatically indexed. The only problem is the millions of submissions you'd get each day.
Slashdot Mirror
Too right, I saw the article title and thought this, you just beat me to it.
.sig here.
Who just moderated this as flame bait? I think it is a perfectly valid point.
Oooh, I hope some one lets me meta moderate that comment.
No matter what it looks like, there isn't a
In away this alternative already exists, https. If everyone starts serving their content from https servers how does filtering work? Since any rating information within the page is encrypted you have to decrypt the packets to see what is being sent. This is bad news for e-commerce, if packets are thrown away because they aren't understood or the encryption used is trivial, who is going to be happy about sending private info across the net?
... to transmit what ever information I want? Designing a reliable transmission protocol on top of UDP is really rather trivial.
.sig here.
What happens if sites are rated according to IP address, this then fails for virtual servers, multi user services etc.
Finally, in the event that they do this, what is to stop me designing and implementing my own protocol on top of TCP, UDP,
No matter what it looks like, there isn't a
This depends on how you implement the cache, fully associative, set associative or what's the other one again?
Typically (memory) caches in PC's are set associative, therefore making the cache larger wouldn't have an adverse effect. Same number of sets, just a larger associative lookup for that set. All it means is more transistors -> more expensive. Even if you increase the number of sets there is no negative effect, since a cache calculates the area of cache to be checked using the memory address.
Overall, a cache will complete it's lookup in one clock cycle no matter how large it is.
No matter what it looks like, there isn't a
The original [British] government bill on electronic commerce required a third party to hold a key for any encrypted message - ie key escrow. I recall a certain large software company strongly endorsing the proposals...
.sig here.
No matter what it looks like, there isn't a
Nah! Nah! Read it before it got posted here :) I found it really rather funny. I'd love to see this made into an episode, maybe one that gets a web broadcast, that'd be really cool!
James
On that topic: surely this could actually done by the web browser rather than a distributed client. If you have a page online you're bound to check it yourself to make sure it's OK. With an appropriate browser or plugin your page could then be indexed and submitted to a search engine. And then once you start surfing any page you visit could be automatically indexed. The only problem is the millions of submissions you'd get each day.
Ooops, silly question by me. Should have read the article properly. I'm sure my A-Level chemistry should have told me that :)
Since oil is decomposed creatures does thi imply that there was once life on Titan?