X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/blobdiff_plain/370e99ebd7a6f15e36330d51d17b3a6ffb8294d9..bec1782b8f23e686f8555a50599e81fff33eb7ab:/blog/index.rss?ds=sidebyside diff --git a/blog/index.rss b/blog/index.rss index ddcb112d2d..582dba0b35 100644 --- a/blog/index.rss +++ b/blog/index.rss @@ -6,6 +6,39 @@ http://people.skolelinux.org/pere/blog/ + + Web service to look up HP and Dell computer hardware support status + http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html + http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html + Wed, 6 Jun 2012 23:15:00 +0200 + <p>A few days ago +<a href="http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html">I +reported how to get</a> the support status out of Dell using an +unofficial and undocumented SOAP API, which I since have found out was +<a href="http://lists.us.dell.com/pipermail/linux-poweredge/2012-February/045959.html">discovered +by Daniel De Marco in february</a>. Combined with my web scraping +code for HP, Dell and IBM +<a href="http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html">from +2009</a>, I got inspired and wrote +<a href="https://views.scraperwiki.com/run/computer-hardware-support-status/">a +web service</a> based on Scraperwiki to make it easy to look up the +support status and get a machine readable result back.</p> + +<p>This is what it look like at the moment when asking for the JSON +output: + +<blockquote><pre> +% GET <a href="https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1">https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1</a> +supportstatus({"servicetag": "2v1xwn1", "warrantyend": "2013-11-24", "shipped": "2010-11-24", "scrapestamputc": "2012-06-06T20:26:56.965847", "scrapedurl": "http://143.166.84.118/services/assetservice.asmx?WSDL", "vendor": "Dell", "productid": ""}) +% +</pre></blockquote> + +<p>It currently support Dell and HP, and I am hoping for help to add +support for other vendors. The python source is available on +Scraperwiki and I welcome help in adding more features.</p> + + + Kommentar til artikkel i Adresseavisa som omtaler FiksGataMi http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html @@ -874,54 +907,5 @@ keep sending documents in ODF formats.</li> - - The cost of ODF and OOXML - http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html - http://people.skolelinux.org/pere/blog/The_cost_of_ODF_and_OOXML.html - Sat, 26 May 2012 18:00:00 +0200 - <p>I just come across a blog post from Glyn Moody reporting the -claimed cost from Microsoft on requiring ODF to be used by the UK -government. I just sent him an email to let him know that his -assumption are most likely wrong. Sharing it here in case some of my -blog readers have seem the same numbers float around in the UK.</p> - -<p><blockquote> <p>Hi. I just noted your -<a href="http://blogs.computerworlduk.com/open-enterprise/2012/04/does-microsoft-office-lock-in-cost-the-uk-government-500-million/index.htm">http://blogs.computerworlduk.com/open-enterprise/2012/04/does-microsoft-office-lock-in-cost-the-uk-government-500-million/index.htm</a> -comment:</p> - -<p><blockquote>"They're all in Danish, not unreasonably, but even -with the help of Google Translate I can't find any figures about the -savings of "moving to a flexible two standard" as claimed by the -Microsoft email. But I assume it is backed up somewhere, so let's take -it, and the £500 million figure for the UK, on trust." -</blockquote></p> - -<p>I can tell you that the Danish reports are inflated. I believe it is -the same reports that were used in the Norwegian debate around 2007, -and Gisle Hannemyr (a well known IT commentator in Norway) had a look -at the content. In short, the reason it is claimed that using ODF -will be so costly, is based on the assumption that this mean every -existing document need to be converted from one of the MS Office -formats to ODF, transferred to the receiver, and converted back from -ODF to one of the MS Office formats, and that the conversion will cost -10 minutes of work time for both the sender and the receiver. In -reality the sender would have a tool capable of saving to ODF, and the -receiver would have a tool capable of reading it, and the time spent -would at most be a few seconds for saving and loading, not 20 minutes -of wasted effort.</p> - -<p>Microsoft claimed all these costs were saved by allowing people to -transfer the original files from MS Office instead of spending 10 -minutes converting to ODF. :)</p> - -<p>See -<a href="http://hannemyr.com/no/ms12_vl02.php">http://hannemyr.com/no/ms12_vl02.php</a> -and -<a href="http://hannemyr.com/no/ms12.php">http://hannemyr.com/no/ms12.php</a> -for background information. Norwegian only, sorry. :)</p> -</blockquote></p> - - -