Search Results

Search found 2 results on 1 pages for 'myggan'.

Page 1/1 | 1 

• Install ubuntu-11.10-desktop-amd64 with Logitech diNovo Edge

  - by MyGGaN

  I know there are problems (and have been for quite some time) with the diNovo Edge keyboard. The solution could be found easily and often you can use the on-screen keyboard to fix it. Now I'm installing Ubuntu from scratch and the only keyboard I have is my diNovo, am I screwed? You are able to get to System Config during the install process and from there to Accessibility menu where you usually can start the on-screen keyboard. This doesn't work, no keyboard in sight... What if I can do some ninja copy-paste with the mouse?? Nope, no pasting allowed in the feilds: username, password, etc. Is there a chance I can fix this somehow within the .iso file before I create the bootable USB drive I use to install from? Or do I have to buy a keyboard to be able to install Ubuntu?

  Read the article

• close long poll connection, jQuery-ajax

  - by MyGGaN

  Background I use a Tornado-like server with support for long-polls. Each web pages a user clicks around to sets up a long poll to the server like this: $.ajax({ type: 'GET', url: "/mylongpollurl/", dataType: 'application/json', success: function(json) { // I do stuff here }, error: function(xhr, errText, ex) { // If timeout I send a new long-poll request } }); Problem I will now rely on data that I get from Fiddler monitoring all requests made from my browser (FF at the moment). Page 1 is loaded and the long poll request is made, now idling at server side. I click a link to page 2 and that page is loaded and setting up a long poll request, BUT the long poll request from page 1 is still idling at server side (according to Fiddler). This means that I will stack all long poll calls when clicking around the page, thus end up with lots of active connections on the server (or are they maybe sharing connection?) My thoughts - As it's a Tornado-like server (using epoll) it can handle quite a lot of connections. But this fact is not to exploit in my opinion. What I mean is that I prefer not to have a timeout on the server for this case (were the client disappears). - I know those stand alone pages better uses a common head and only swap content via ajax calls but this design we use today was not my call... - The best way to solve this would probably be to have the connection reused (hard to pull off I think) or closed as soon as the browser leaves the page (you click to another page). Thanks -- MyGGaN

  Read the article

1