My daily readings 07/17/2009

  • tags: proxy, android

  • tags: no_tag

    • Are you trying to set the proxy for the device as a whole, or just for

      a specific app?

      If you’re trying to use a proxy from within an application you’re

      working on, I’d recommend looking at

      the API for URL.openConnection(Proxy p); one of the variants of this

      call takes a proxy as an argument.

      I’ve used it and it works quite well.

      If you’re trying to get the device itself to work from behind a proxy

      (i.e. browser, mail, all the built-in apps), I’m

      not sure if it’s possible to do this from the ui without doing some

      fiddling around with adb commands. I’ve only

      gotten this to work from an emulator, by SSH-ing into the device and

      changing some tables in the settings database.

      Never tried from a real device.

  • tags: no_tag

    • Damian does not need fundamentally new software. He does not need a custom application server, nor could you convince him to write one. What he needs is the insight to identify state, cached data and persistent data in his application. Application state goes into an in-memory key-value store like Tokyo Tyrant. Cache data goes into Memcached. Persistent data goes into a database. Note that the seperation of code and application state may be beneficial later, because it allows you to scale easily by adding new memory servers. Mysql will probably need to be left behind for a persistent key-value store that is more easily distributed and replicated. As co-founder of Scalien and one of the developers of our Keyspace replicated key-value store, I can only recommend it. It’s devilishly fast for consistently replicated writes.

      When the server launches, before client requests are served, a script initializes the system by loading the appropriate state data into memory. Client requests are served primarily by using state information (global and per-user, per-game, per-session, etc.), and sometimes persistent data is written back to disk. Data that isn’t absolutely essential, like an in-game chat transcript are written to disk asynchronously in the background.

  • tags: Competition

  • tags: architecture, scalability

      • 16 million page views a month
      • 3 million unique visitors a month (Facebook reaches 77 million unique visitors a month)
      • 6 million visits a month
      • 86% of traffic comes from Google
      • 9 million active programmers in the world and 30% have used Stack Overflow.
      • If you’re comfortable managing servers then buy them. The two biggest problems with renting costs were: 1) the insane cost of memory and disk upgrades 2) the fact that they [hosting providers] really couldn’t manage anything.
      • Make larger one time up front investments to avoid recurring monthly costs which are more expensive in the long term.
    • Memory is incredibly cheap. Max it out for almost free performance. At Dell, for example, upgrading from 4G memory to 128G is $4378.
    • Stack Overflow copied a key part of the Wikipedia database design. This turned out to be a mistake which will need massive and painful database refactoring to fix. The refactorings will be to avoid excessive joins in a lot of key queries. This is the key lesson from giant multi-terabyte table schemas (like Google’s BigTable) which are completely join-free. This is significant because Stack Overflow’s database is almost completely in RAM and the joins still exact too high a cost.
    • At low server volume, the key cost driver is not rackspace, power, bandwidth, servers, or software; it is NETWORKING EQUIPMENT. You need a gigabit network between your DB and Web tiers. Between the cloud and your web server, you need firewall, routing, and VPN devices. The moment you add a second web server, you also need a load balancing appliance. The upfront cost of these devices can easily be 2x the cost of a handful of servers.
  • tags: mobile

  • tags: web, app

    • Vic Gundotra, Google Engineering vice president and developer evangelist, (pictured centre) told the  Mobilebeat conference in  San Francisco on Thursday that the web had won and users of mobile phones would get their information and entertainment from browsers in future.

      He claimed that even Google was not rich enough to support all of the different mobile platforms from Apple’s AppStore to those of the BlackBerry, Windows Mobile, Android and the many variations of the Nokia platform.

    • Mr Gundotra pointed out that the latest version of the Safari Webkit-based browser on the iPhone allowed positioning technology on the phone to be used – Google’s home page can now display where users are located.
    • Mr Gundotra said even Steve Jobs, Apple’s chief executive, had said “Build for the web,” when the iPhone was launched, but the idea had met with resistance from developers at the time.

      The timing was not right, he suggested, but “the rate of innovation in the browser [over the past 12 months] is surprising.”

      “I think Steve really did understand that, over the long term, it would be the web, and I think that’s how things will play out.”

  • tags: bluetooth, tether

  • tags: Android, port, forwarding

  • tags: SSH, Client

  • tags: android, proxy

Posted from Diigo. The rest of my favorite links are here.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: