Search Results

Search found 32459 results on 1299 pages for 'no internet connection'.

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

Page 362/1299 | < Previous Page | 358 359 360 361 362 363 364 365 366 367 368 369  | Next Page >

  • Google Denied Trademark for Nexus One

    <b>Datamation:</b> "Google doesn't get embarrassed too often, but the U.S. Patent and Trademark Office (USPTO) just dealt it a loss of face by rejecting its application for a trademark for the Nexus One smartphone."

    Read the article

  • How to get Linux in your office

    <b>Tux Radar:</b> "And with Linux and free software making a name for itself in the world of big business, many more people are testing the feasibility of switching small and home office software to their open source equivalents."

    Read the article

  • Sockets with Silverlight 4

    - by AngryHacker
    I need to implement a persistent socket connection from my in-browser Silverlight 4 app to a device on the network. I need the following: Connect to it and keep a persistent connection Send and Receive data Get some type of event or notification (or detect it) when the connection drops. Is this possible with Silverlight 4? If so, can someone point me to some examples? All I am finding are some attempts at it with Silverlight 2.

    Read the article

  • Java resource closing

    - by Bob
    Hi, I'm writing an app that connect to a website and read one line from it. I do it like this: try{ URLConnection connection = new URL("www.example.com").openConnection(); BufferedReader rd = new BufferedReader(new InputStreamReader(connection.getInputStream())); String response = rd.readLine(); rd.close(); }catch (Exception e) { //exception handling } Is it good? I mean, I close the BufferedReader in the last line, but I do not close the InputStreamReader. Should I create a standalone InputStreamReader from the connection.getInputStream, and a BufferedReader from the standalone InputStreamReader, than close all the two readers? I think it will be better to place the closing methods in the finally block like this: InputStreamReader isr = null; BufferedReader br = null; try{ URLConnection connection = new URL("www.example.com").openConnection(); isr = new InputStreamReader(connection.getInputStream()); br = new BufferedReader(isr); String response = br.readLine(); }catch (Exception e) { //exception handling }finally{ br.close(); isr.close(); } But it is ugly, because the closing methods can throw exception, so I have to handle or throw it. Which solution is better? Or what would be the best solution?

    Read the article

  • Humble Indie Bundle Shows GNU/Linux Gaming Statistics

    <b>Inatux:</b> "Games have become the topic of late. Osmos developers wonder whether there is enough market share for GNU+Linux game ports to be worth the cost, but they aren't the only ones. It's been discussed time and time again, is a GNU+Linux -- or really any Unix or Unix-like -- port worth it?"

    Read the article

facebook twitter digg google delicious technorati stumbleupon myspace wordpress linkedin gmail igoogle windows live tumblr viadeo yahoo buzz yahoo mail yahoo bookmarks favorites email print

< Previous Page | 358 359 360 361 362 363 364 365 366 367 368 369  | Next Page >