Even with bad WiFi, your RTT should still be an order of magnitude smaller than on the 3G network. I suppose it also depends on your 3G network. I am in the UK and my service works well enough that I don't have to bother finding WiFi spots at all, I just use 3G.
Mobile operators collect CDRs on the terrestrial side of the GGSN. Even if over the air there are no retransmissions, there will still be some on the IP network. I work for a provider with higher RTTs (~1200ms) and the extra 5% is pretty much what we are seeing. We all use the same TCP splitting techniques (Vegas on the slow link and Reno on the fast link), because the primary purpose is to improve the user experience.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page. Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience would be 4 times as slow.
Also, most people have no idea of the optimization techniques operators use.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page. Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience would be 4 times as slow.
Also, most people have no idea of the optimization techniques operators use.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page. Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience would be 4 times as slow.
Indeed, all sorts of TCP splitting techniques exist. However, there is only so much data such a device can temporarily queue to keep retransmission on the terrestrial side. If you run a network with 10 million subscribers, it becomes very interesting.
The mismatch comes from the fact that operators collect CDRs on the terrestrial side of their GGSNs. So even if the mobile subscriber does not need to resend a segment, the terrestrial retransmission is still accounted, as are the duplicate ACKs sent by the Internet host.
You simply can't expect both having the cake and eating it. High latency links come with trade-offs.
I work for a provider with much higher RTTs (~1200ms). The 5% reported by the study is exactly what we are seeing.
I wish I could agree with, but I can't. You see, Facebook uses the single most readily available resource humanity has - mediocrity, an outlet of which it essentially is. The vast majority of people are simply statistics. Nobody knows or cares about them except maybe for their relatives and a handful of acquaintances. Every like they get, every stupid comment on a picture they post compensates for their lack of self esteem and fuels their exhibitionism. Facebook it's not something you grow out of, but rather something you grow old into, because the older you get, the better you realize you're not worth much.
You apply good ol' fashioned logic where there usually is none. Nowadays, people mostly buy things because they are affordable, not because they are necessary. If this gizmo is affordable, it will sell.
Slashdot Mirror
Besides, who in their right mind would seek this level of counseling on Slashdot?
And this is one.
I was reading something in a different tab at the same time.
Even with bad WiFi, your RTT should still be an order of magnitude smaller than on the 3G network.
I suppose it also depends on your 3G network. I am in the UK and my service works well enough that
I don't have to bother finding WiFi spots at all, I just use 3G.
Mobile operators collect CDRs on the terrestrial side of the GGSN. Even if over the air there are no retransmissions,
there will still be some on the IP network. I work for a provider with higher RTTs (~1200ms) and the extra 5% is pretty
much what we are seeing. We all use the same TCP splitting techniques (Vegas on the slow link and Reno on the
fast link), because the primary purpose is to improve the user experience.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page.
Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy
fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as
above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience
would be 4 times as slow.
Whoops, replied to myself a 2nd time instead.
Also, most people have no idea of the optimization techniques operators use.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page.
Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy
fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as
above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience
would be 4 times as slow.
Also, most people have no idea of the optimization techniques operators use.
Navigate to any content heavy website. If your mobile browser allows you to, try to see the source of the page.
Chances are you will see all whitespace trimmed, all CSS and JS inlined. All pictures are compressed in a lossy
fashion to reduce their size.
There is also HTTP request coalescing. If you request "/", the whole page will be retrieved, then processed as
above and delivered to the mobile browser in a single reply. How many GET requests do you save? A lot.
If there were no such techniques, one's mobile bill would be almost twice as high and the browsing experience
would be 4 times as slow.
Indeed, all sorts of TCP splitting techniques exist. However, there is only so much data such a device can temporarily queue to keep retransmission on the terrestrial side. If you run a network with 10 million subscribers, it becomes very interesting.
The mismatch comes from the fact that operators collect CDRs on the terrestrial side of their GGSNs. So even if the mobile subscriber does not need to resend a segment, the terrestrial retransmission is still accounted, as are the duplicate ACKs sent by the Internet host.
You simply can't expect both having the cake and eating it. High latency links come with trade-offs.
I work for a provider with much higher RTTs (~1200ms). The 5% reported by the study is exactly what we are seeing.
24 Hz displays (theaters, yes, they do integer multiples) will be fine.
30 Hz displays (shitty TVs) will fuck it up royally.
24 Hz displays (theaters) will be fine.
60 Hz displays (TVs) will fuck it up royally.
120 Hz displays (TVs) will fuck it up royally.
Don't you see copy protection when you see it?
But if you were one, would you feel comfortable as 131916?
I wish I could agree with, but I can't. You see, Facebook uses the single most readily available resource humanity has - mediocrity, an outlet of which it essentially is. The vast majority of people are simply statistics. Nobody knows or cares about them except maybe for their relatives and a handful of acquaintances. Every like they get, every stupid comment on a picture they post compensates for their lack of self esteem and fuels their exhibitionism. Facebook it's not something you grow out of, but rather something you grow old into, because the older you get, the better you realize you're not worth much.
Because simply saying "look, I can do mediocre stuff in Blender" is so passé.
... how do they know you are? Well, if your profile is public, then you deserve it, moron.
A Steve Jobs, but humble.
Slashdotters aren't likely to run into that particular problem.
Q: How do you get rid of onion breath?
A: Eat some garlic.
With a brand name like that, it was only a matter of time, really.
Yes, it's really disturbing. Everytime I shop there I see people buying them.
http://www.guardian.co.uk/technology/2010/nov/19/facebook-credits-game-tesco
In the UK you can buy Facebook credits at every Tesco supermarket. I'm sure others sell them too.
It eventually fell off the cliff.
Let's be humane. Let's trigger the blow with a polygraph.
You apply good ol' fashioned logic where there usually is none. Nowadays, people mostly buy things because they are affordable, not because they are necessary. If this gizmo is affordable, it will sell.
Caffeine much? Sorry, didn't observe the title bar.
http://source.android.com/source/downloading.htmlCheck yields a 404.
Is a joke that needs to be explained a good or a bad joke? :-)