<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/topics-files/atom2xhtml.xsl" type="text/xsl"?>
<!-- This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers. -->
<feed xmlns="http://www.w3.org/2005/Atom"
><title
>Blog@Case Topics: Computing</title
><link rel="self" href="http://blog.case.edu/topics/Computing"
 /><id
>http://blog.case.edu/topics/Computing</id
><category term="Computing" label="Computing"
 /><link rel="related" href="http://blog.case.edu/topics/computing" title="computing"
 /><link rel="related" href="http://blog.case.edu/topics/open%20source" title="open source"
 /><link rel="related" href="http://blog.case.edu/topics/wiki" title="wiki"
 /><link rel="related" href="http://blog.case.edu/topics/google" title="google"
 /><link rel="related" href="http://blog.case.edu/topics/mediawiki" title="mediawiki"
 /><link rel="related" href="http://blog.case.edu/topics/case%20it" title="case it"
 /><link rel="related" href="http://blog.case.edu/topics/xml" title="xml"
 /><link rel="related" href="http://blog.case.edu/topics/atom" title="atom"
 /><link rel="related" href="http://blog.case.edu/topics/iphone" title="iphone"
 /><link rel="related" href="http://blog.case.edu/topics/internet" title="internet"
 /><link rel="related" href="http://blog.case.edu/topics/osso" title="osso"
 /><contributor
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></contributor
><contributor
><name
>Nicole Sharp</name
><email
>nicole.sharp@case.edu</email
><uri
>http://blog.case.edu/nss10</uri
></contributor
><contributor
><name
>Steven Hauck</name
><email
>steven.hauck@case.edu</email
><uri
>http://blog.case.edu/sah33</uri
></contributor
><contributor
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/hac4</uri
></contributor
><updated
>2007-06-25T14:00:02Z</updated
><entry
><title
>Photo Challenge</title
><link href="http://blog.case.edu/hac4/2007/08/29/photochallenge"
 /><id
>http://blog.case.edu/hac4/2007/08/29/photochallenge</id
><published
>2007-08-30T04:00:22Z</published
><updated
>2007-08-30T04:52:45Z</updated
><category term="computing" label="computing"
 /><category term="events" label="events"
 /><category term="musings" label="musings"
 /><category term="photography" label="photography"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<p class="photoright">
<img alt="snyder.jpg" src="http://blog.case.edu/hac4/2007/08/29/snyder.jpg" width="240" height="159" />
<br />
<img alt="piper.jpg" src="http://blog.case.edu/hac4/2007/08/29/piper.jpg" width="240" height="159" />
<br />
<img alt="lev.jpg" src="http://blog.case.edu/hac4/2007/08/29/lev.jpg" width="240" height="159" />
<br />
<img alt="tubbsjones.jpg" src="http://blog.case.edu/hac4/2007/08/29/tubbsjones.jpg" width="240" height="159" />
</p>
<p>While I was taking pictures today&#8212;at the 
<a href="http://www.case.edu/convocation/">2007 Annual Fall Convocation + Investiture Ceremony for president Barbara R. Snyder</a>&#8212;
<a href="http://blog.case.edu/lev.gonick/">Lev Gonick</a> joked that he wanted to see the pictures up on my blog by the time the event was done.</p>
<p>Naturally that wasn't possible, I can't upload and shoot at the same time. In fact having taken over 400 photos I only have half of them up on Flickr now and will have to finish the rest on Thursday. (At which point I'll post the link.)</p>
<p>But the suggestion got me thinking; what tools would I have needed to make that possible? To that end I've got up with a list of requirements, most of which could probably be created by a team from our own campus.</p>
<ul>
<li>Bluetooth (or similar) enabled camera that could download images while I am still shooting new ones.</li>
<li>Laptop, or preferably a smaller wireless device that could run a program to access the camera, grab the images, store them in some logical manner, then trigger another program to</li>
<li>Pick out a small selection of the most interesting or aesthetically pleasing images, upload them to the blog server and include them in a new entry.</li>
</ul>
<p>Some of this is already possible. The sticking points are:</p>
<ol>
<li>That it all has to happen while I am still taking additional pictures. Thus I would want to be able to push a button or start a program via a few simple commands then stick the device back in my pocket to be ignored while I keep taking pictures. (I could set parameters such as number of photos to blog, size, etc. in advance.) Conversely the process could be built into the camera which would access the wireless network and upload them all to be stored on Flickr (or the Blog server or somewhere else online) then trigger the rest of the process to happen on the server.</li>
<li>Developing a program that could objectively choose the most interesting photos. Given that such choices are often subjective rather than objective I think this would be the most challenging part. But if we had an interdisciplinary team including programmers engineers and faculty/students from Cognitive Science and Art they might be able to create something that could get it right most of the time. It would certainly be interesting to see which shots a program would choose in comparison to which shots were most often chosen by people.</li>
</ol>
<p>What do you think Lev? (And of course everyone else.)</p>
</div
></content
><author
><name
>Heidi Cool</name
><email
>heidi.cool@case.edu</email
><uri
>http://blog.case.edu/hac4</uri
></author
></entry
><entry
><title
>Obligatory Post on the iPhone</title
><link href="http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone"
 /><id
>http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone</id
><published
>2007-06-25T14:00:00Z</published
><updated
>2007-06-25T14:00:02Z</updated
><category term="AT&amp;T" label="AT&amp;T"
 /><category term="Apple" label="Apple"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="iPhone" label="iPhone"
 /><category term="internet" label="internet"
 /><category term="technology" label="technology"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>First off, congratulations to Apple and Steve Jobs for creating such a frenzy over a device that only few have actually seen being operated. There are few companies in the world that can generate this much anticipation for a product. Hats off to you. Because I live in Silicon Valley, everything tech is amplified about 100x compared to most parts of the country/world. And, since Apple's headquarters are only a few miles away (I think it is less than 3 miles from my apartment), the iPhone hype here has been almost untolerable. Everywhere you look, iPhone this, iPhone that. Every blog. iPhone. iPhone. iPhone. June 29 is almost here. Cingular (I guess it is the "new AT&amp;T" now), is preparing for people to be camping out overnight to be the first to get their hands on the devices. It is sheer madness. All of this excitement over a portable electronic device! Fortunately for my sanity, I've managed to remain calm about the iPhone. The reason is I don't want one. Well, technically, I'd like one, but I won't be buying one. My reasons are plentiful. Here are the top three:
<ul>
<li>The iPhone doesn't have a detachable battery -- Seriously, WTF? It is one thing for my iPod to run out of battery (which it does very often since I have almost exhausted the usable life out of the battery), it is another to run out of battery on my phone. Even if the battery life is great (I'm a little skeptic about the 
<a href="http://www.apple.com/iphone/specs.html">advertised battery life</a>), I still want the ability to change the battery. When the battery eventually loses its charge capacity, I want the freedom to replace it without replacing the whole device.</li>
<li>No 3G -- The non-WIFI network speed of the non-3G iPhone will be pathetic. Currently, most of AT&amp;T's EDGE network averages about 40kbps -- slower than a 56k dial-up modem! AT&amp;T has been upgrading their network lately to try to boost performance to 80kbps -- slightly faster than a 56k modem. Even if they max out, they can only get max performance at about 4x 56k speeds. The WIFI connection is a different story. It will probably be able to go over 1Mbps (5x faster than max EDGE speed). Of course, when you are in the store doing all the cool online activities with the iPhone, it will be going over WIFI. I picture many customers walking out of the store and saying, "why is the network so slow now?". They will find out that they have to use WIFI for a better browsing experience. Of course, WIFI will drain your battery like nothing else. So, you will either get great network performance or longer battery life. I don't want to make that decision! It will be interesting to see how many initial buyers complain about the EDGE network speed. With Google Maps on EDGE now, I find it barely usable. Will it be the same on iPhone? Time will tell.</li>
<li>It is the first model -- If I've learned anything about Apple products, it is to wait for the second model. There will be so many software refinements and hardware improvements, that you will be glad you waited. I wouldn't be surprised if a second generation was available by February 2008.</li>
</ul>In summary, being an early adopted of this product is just too risky or foolish for me. I commend Apple at designing an amazing product and building anticipation, but I just can't buy one just yet. Once the dust settles and iPhone survives the test of time (and adds a few more features, like 3G), I will probably be in the market for an iPhone, or any of the numerous competitors that are quickly entering the market. Finally, I wish the early adopters good luck. You will drop and good chunk of change on the device and service plan. I hope you get a great return on your investment.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Obligatory Post on the iPhone</title
><link href="http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone"
 /><id
>http://blog.case.edu/gps10/2007/06/25/obligatory_post_on_the_iphone</id
><published
>2007-06-25T14:00:00Z</published
><updated
>2007-06-25T14:00:02Z</updated
><category term="AT&amp;T" label="AT&amp;T"
 /><category term="Apple" label="Apple"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="iPhone" label="iPhone"
 /><category term="internet" label="internet"
 /><category term="technology" label="technology"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>First off, congratulations to Apple and Steve Jobs for creating such a frenzy over a device that only few have actually seen being operated. There are few companies in the world that can generate this much anticipation for a product. Hats off to you. Because I live in Silicon Valley, everything tech is amplified about 100x compared to most parts of the country/world. And, since Apple's headquarters are only a few miles away (I think it is less than 3 miles from my apartment), the iPhone hype here has been almost untolerable. Everywhere you look, iPhone this, iPhone that. Every blog. iPhone. iPhone. iPhone. June 29 is almost here. Cingular (I guess it is the "new AT&amp;T" now), is preparing for people to be camping out overnight to be the first to get their hands on the devices. It is sheer madness. All of this excitement over a portable electronic device! Fortunately for my sanity, I've managed to remain calm about the iPhone. The reason is I don't want one. Well, technically, I'd like one, but I won't be buying one. My reasons are plentiful. Here are the top three:
<ul>
<li>The iPhone doesn't have a detachable battery -- Seriously, WTF? It is one thing for my iPod to run out of battery (which it does very often since I have almost exhausted the usable life out of the battery), it is another to run out of battery on my phone. Even if the battery life is great (I'm a little skeptic about the 
<a href="http://www.apple.com/iphone/specs.html">advertised battery life</a>), I still want the ability to change the battery. When the battery eventually loses its charge capacity, I want the freedom to replace it without replacing the whole device.</li>
<li>No 3G -- The non-WIFI network speed of the non-3G iPhone will be pathetic. Currently, most of AT&amp;T's EDGE network averages about 40kbps -- slower than a 56k dial-up modem! AT&amp;T has been upgrading their network lately to try to boost performance to 80kbps -- slightly faster than a 56k modem. Even if they max out, they can only get max performance at about 4x 56k speeds. The WIFI connection is a different story. It will probably be able to go over 1Mbps (5x faster than max EDGE speed). Of course, when you are in the store doing all the cool online activities with the iPhone, it will be going over WIFI. I picture many customers walking out of the store and saying, "why is the network so slow now?". They will find out that they have to use WIFI for a better browsing experience. Of course, WIFI will drain your battery like nothing else. So, you will either get great network performance or longer battery life. I don't want to make that decision! It will be interesting to see how many initial buyers complain about the EDGE network speed. With Google Maps on EDGE now, I find it barely usable. Will it be the same on iPhone? Time will tell.</li>
<li>It is the first model -- If I've learned anything about Apple products, it is to wait for the second model. There will be so many software refinements and hardware improvements, that you will be glad you waited. I wouldn't be surprised if a second generation was available by February 2008.</li>
</ul>In summary, being an early adopted of this product is just too risky or foolish for me. I commend Apple at designing an amazing product and building anticipation, but I just can't buy one just yet. Once the dust settles and iPhone survives the test of time (and adds a few more features, like 3G), I will probably be in the market for an iPhone, or any of the numerous competitors that are quickly entering the market. Finally, I wish the early adopters good luck. You will drop and good chunk of change on the device and service plan. I hope you get a great return on your investment.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Songbird Media Player</title
><link href="http://blog.case.edu/gps10/2006/10/15/songbird_media_player"
 /><id
>http://blog.case.edu/gps10/2006/10/15/songbird_media_player</id
><published
>2006-10-16T00:02:36Z</published
><updated
>2006-10-16T00:06:30Z</updated
><category term="Computing" label="Computing"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I just discovered 
<a href="http://www.songbirdnest.com/">Songbird</a>, a cross-playform (Windows, Mac, Linux) media player/iTunes clone. It is still in pre-release, but it looks very promising. I was disappointed to see it doesn't read Musepack files, but it is light years ahead of anything on Linux in terms of the UI. My only other complaint is it seems a bit bloated. Time will tell. I am eager to wait for it to develop and see what extensions people make.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>KeyServer Strikes Again</title
><link href="http://blog.case.edu/nss10/2006/04/05/keyserver_strikes_again"
 /><id
>http://blog.case.edu/nss10/2006/04/05/keyserver_strikes_again</id
><published
>2006-04-05T19:56:24Z</published
><updated
>2006-04-13T11:52:55Z</updated
><category term="Computing" label="Computing"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Dear Software Center, All I wanted to do was some simple data analysis in Matlab on the data I spent seven hours collecting on Saturday. Is that so much to ask? According to your website, Matlab users need only have a network connection to use the program. My laptop is currently hardwired into the Case network, and, yet, I am getting nasty error messages from KeyServer, which isn't supposed to have anything to do with Matlab anyway. Do you want me to download a newer version? Is that it? I'm supposed to spend my afternoon downloading a 1.18 GB file and reinstalling one of the largest programs on my computer, am I? I'm a busy person, Software Center, and this is not at all funny. It still won't be funny tomorrow morning when I have to go tell my advisor that I don't have results for him because Matlab refuses to load. So do you think we can possibly move things along? This doesn't have to be difficult or painful. Thanks! Nicole Sharp 
<b>ETA:</b> The KeyServer server hiccuped and Matlab blew up on me. The new installation involved infinite loops. I had to go into safe mode to fix things. But all is now well because Matlab works again.</div
></content
><author
><name
>Nicole Sharp</name
><email
>nicole.sharp@case.edu</email
><uri
>http://blog.case.edu/nss10</uri
></author
></entry
><entry
><title
>Why I Love KDE</title
><link href="http://blog.case.edu/gps10/2006/01/12/why_i_love_kde"
 /><id
>http://blog.case.edu/gps10/2006/01/12/why_i_love_kde</id
><published
>2006-01-12T19:10:13Z</published
><updated
>2006-01-12T19:23:28Z</updated
><category term="Computing" label="Computing"
 /><category term="open source" label="open source"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>After a long hard day of working on house improvement and computer projects yesterday, I decided to poke around 
<a href="http://www.kde.org">KDE</a> a bit. You always hear about Windows and OS X as the two competing desktops. After using KDE as my primary desktop for about six months now, considering the work I do, I wouldn't trade it in for anything. KDE has every feature that a programmer or well-organized person could want. As a programmer, it increases my productivity. There is no question why I prefer to work from home and use my KDE desktop environment. 
<big>
<big>What I love best about KDE</big>
</big>
<ul>
<li>Built-in protocol handlers (e.g. sftp:// ftp:// http:// samba:// webdav://). These protocols can be used in ANY KDE application to open and save files. Do you know how easy it is to work with remote files this way!! No more manual FTP commands after every save!</li>
<li>It comes with an application to do everything. The best part about it, everything works together. For example, the time-tracking application, 
<a href="http://pim.kde.org/components/karm.php">KArm</a> integrates with KOrganizer, which can be set up to integrate with 3rd party groupware utilities, such as eGroupware, Kolab, SLOX, or Novel Groupwise.</li>
</ul>I'm writing this entry during a period of euphoria, as I just discovered more cool applications that KDE ships with. Next time someone tells me how cool Vista or OS X looks, I'll just laugh to myself. KDE is more productive than anything. Period. Now let's see who is laughing when I can get more work done and earn more $$$.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Research computing - High performance?</title
><link href="http://blog.case.edu/sah33/2006/01/02/research_computing_high_performance"
 /><id
>http://blog.case.edu/sah33/2006/01/02/research_computing_high_performance</id
><published
>2006-01-02T20:00:00Z</published
><updated
>2006-01-02T20:09:24Z</updated
><category term="Case" label="Case"
 /><category term="Computing" label="Computing"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>One of the things that I am interested in, primarily because it helps me do my research better, is high-performance computing. I have only been here at Case a few years, but issues of research computing have been around here a while I gather... The primary issue is often: 
<strong>
<u>is there enough</u>
</strong>? It isn't always clear what 
<u>enough</u> means. What is enough for my research group might be overkill for another researcher, or not even scratch the surface of the needs of yet another. High-performance may mean fast CPU's to me, but super-fast networks, incredibly high-speed access to enormous datasets, or screaming 3-D visualization tools to others. So what? Well, a lot of great research comes from being at the edge of what is possible... but computational resources are expensive - especially at the edge and primarily because they become obsolete so quickly. It is not like buying lab supplies that could work for a decade or more if properly maintained, etc - optimistically, 3 years and a computer is toast. So, is there potentially an economy of scale that could allow more researchers to be closer to the cutting-edge and really expand research opportunities? Research units working together to share computational resources could be a good thing. But what would make it 
<strong>good</strong> for researchers with few (no) ties other than that they use computers throwing in their resources together? I think there are three aspects to an answer to this question: (1) Can we do better, more cutting-edge research? (2) Can the workloads, related to computational infrastructure, of individual researchers or research groups be reduced? (3) Is it financially sustainable? All important questions, but the one that interests me most right now is (1). 
<em>
<strong>What research could you pursue (that you can't do now) if there were significantly more resources available to you on campus than a single department (or researcher) might garner by themselves?</strong>
</em> Nice to think far forward like that. The 
<a href="http://www.case.edu/its/researchcomputing/acrc.htm">ACRC</a> is thinking about this question too... anyone else?</div
></content
><author
><name
>Steven Hauck</name
><email
>steven.hauck@case.edu</email
><uri
>http://blog.case.edu/sah33</uri
></author
></entry
><entry
><title
>GRE Practice Test Frustrations</title
><link href="http://blog.case.edu/nss10/2005/11/05/gre_practice_test_frustrations"
 /><id
>http://blog.case.edu/nss10/2005/11/05/gre_practice_test_frustrations</id
><published
>2005-11-05T15:31:29Z</published
><updated
>2005-11-05T15:40:35Z</updated
><category term="Computing" label="Computing"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I purposefully got up early this morning (for a college student, at least) so that I would have time to take one of the 
<a href="http://www.ets.org/portal/site/ets/menuitem.1488512ecfd5b8849a77b13bc3921509/?vgnextoid=302b66f22c6a5010VgnVCM10000022f95190RCRD&amp;vgnextchannel=d687e3b5f64f4010VgnVCM10000022f95190RCRD">full length computer-based practice tests</a> they have on the GRE website. I download the software, install, and open it, only to discover that it's worthless to me. Their PowerPrep software 
<i>requires</i> that the moniter be set to 640 x 480 pixels, and the lowest resolution my laptop's moniter is capable of is 800 x 600. This means that, when I, say, open the practice test, I can see the first half a line of both of the writing questions, but I can't get the gist of either of them, nor can I see any way to navigate so that I can answer the question or escape the test I'm not capable of answering. This is entirely too frustrating. I'm going to have to go do something like install this program in Nord and sit there for four hours just to take a practice exam and get an idea of what my scores are likely to be. Not that I have five hours laying around to just go do that...</div
></content
><author
><name
>Nicole Sharp</name
><email
>nicole.sharp@case.edu</email
><uri
>http://blog.case.edu/nss10</uri
></author
></entry
><entry
><title
>Squirrelmail</title
><link href="http://blog.case.edu/gps10/2005/10/27/squirrelmail"
 /><id
>http://blog.case.edu/gps10/2005/10/27/squirrelmail</id
><published
>2005-10-28T03:46:19Z</published
><updated
>2005-10-28T03:49:38Z</updated
><category term="Case IT" label="Case IT"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="open source" label="open source"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I have set up a 
<a href="http://www.squirrelmail.org">SquirrelMail</a> installation for Case users at 
<a href="https://opensource.case.edu/squirrelmail/">https://opensource.case.edu/squirrelmail/</a>. Enjoy the highly customizable webmail interface. IMO, it is much better than what we have now. Yay for IMAP standards.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Squirrelmail</title
><link href="http://blog.case.edu/gps10/2005/10/27/squirrelmail"
 /><id
>http://blog.case.edu/gps10/2005/10/27/squirrelmail</id
><published
>2005-10-28T03:46:19Z</published
><updated
>2005-10-28T03:49:38Z</updated
><category term="Case IT" label="Case IT"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="open source" label="open source"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I have set up a 
<a href="http://www.squirrelmail.org">SquirrelMail</a> installation for Case users at 
<a href="https://opensource.case.edu/squirrelmail/">https://opensource.case.edu/squirrelmail/</a>. Enjoy the highly customizable webmail interface. IMO, it is much better than what we have now. Yay for IMAP standards.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>It's Time to Emancipate Computer Help Documentation</title
><link href="http://blog.case.edu/gps10/2005/10/27/its_time_to_emancipate_computer_help_documentation"
 /><id
>http://blog.case.edu/gps10/2005/10/27/its_time_to_emancipate_computer_help_documentation</id
><published
>2005-10-27T22:13:31Z</published
><updated
>2005-10-27T22:43:28Z</updated
><category term="Computing" label="Computing"
 /><category term="Wiki" label="Wiki"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>This post is spurred by 
<a href="http://acm.cwru.edu/pipermail/sigmac-talk/2005-October/001911.html">the latest sigmac-talk mailing list thread about printing to Wade</a>. For months now, Apple users at Case have griped about not being able to print to Wade using OS X 10.4 Tiger. The issue was 
<a href="http://acm.cwru.edu/pipermail/sigmac-talk/2005-September/001863.html">first raised</a> with optimism. The thread chronicles guarantees of the posting of the updated instructions on 
<a href="http://help.case.edu">help.case.edu</a>. However, those instructions were never posted and people are still having trouble. The solution to the problem: The 
<a href="http://wiki.case.edu/Main_Page">Case Wiki</a> (see 
<a href="http://wiki.case.edu/printing">printing</a> for our developing solution for this particular problem). 95% of 
<a href="http://help.case.edu">help.case.edu</a> is instructions and reference material. Although the material is well laid-out and easy-to-follow, there is one major problem: accessibility. As our chronicles with printing to Wade from Tiger have shown us, the site is not frequently updated and it is difficult to push through updates. The information published at 
<a href="http://help.case.edu">help.case.edu</a> is ripe for wikification. It makes perfect sense to convert ALL of the reference information located there to the 
<a href="http://wiki.case.edu/Main_Page">Case Wiki</a>. When 
<a href="http://wiki.case.edu/ITS">ITS</a> changes something, why should they have to go through a middleman to make changes to the (un)official instructions at help.case.edu? Shouldn't they have access to the documentation for their own projects and services? Shouldn't they be able to change the instructions at the exact same time a change in a service is made? By publishing this material on a wiki, we would also open up a conduit of communication between system operators and end-users. End-users could comment on the instructions, express issues using the instructions, and, of course, modify the instructions to make them easier to follow. Converting content over to the wiki is no small task. There are countless pages of content and numerous images. However, the end result is worth the trouble, as it is for the benefit of the end-user, which is, after all, the pillar on which customer support and the 
<a href="http://wiki.case.edu/Help_Desk">Help Desk</a> rest.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Google Blog Search Makes Searching Public Opinion Easy</title
><link href="http://blog.case.edu/gps10/2005/09/26/google_blog_search_makes_searching_public_opinion_easy"
 /><id
>http://blog.case.edu/gps10/2005/09/26/google_blog_search_makes_searching_public_opinion_easy</id
><published
>2005-09-26T21:13:11Z</published
><updated
>2005-09-26T21:33:52Z</updated
><category term="ATOM" label="ATOM"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="Google" label="Google"
 /><category term="RSS" label="RSS"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Google released 
<a href="http://blogsearch.google.com">Blog Search</a> a few weeks ago. In short, it is a search performed on 
<a href="http://wiki.case.edu/syndicated_feeds">syndicated feeds</a> on the internet. These feeds are often associated with blogs, but they are also heavily used on informational sites. The feeds themselves can be used to convey a wide range of information. There are two things I really love about Google Blog Search:
<ol>
<li>The content being indexed by Google is highly dynamic and Google updates it frequently. Unlike the regular Google search that indexes results by relevance, the blog search can index results by date retrieved. Not only do you find recent changes, but you can find obscure sources of information.</li>
<li>Search results are available in 
<a href="http://wiki.case.edu/RSS">RSS</a> and 
<a href="http://wiki.case.edu/ATOM">ATOM</a>. This just rocks</li>
</ol>For an institution such as the university that is always cognizant of its public portrayal, Google Blog Search is an invaluable tool. If you are one of these people, you might be interested in the 
<a href="http://blogsearch.google.com/blogsearch?hl=en&amp;utm_source=AdWords&amp;utm_campaign=us-ha-en-blogsearch&amp;utm_term=blog+search&amp;utm_medium=cpc&amp;utm_content=googleblogsearch&amp;q=%22case+western%22&amp;btnG=Search+Blogs&amp;scoring=d">Google Blog Search results for 'Case Western'</a>. Drop the feed of this search result in your favorite aggregator, and you are subscribed to a public opinion pole/news site about Case. It was quite interesting when I saw 
<a href="http://www.discourse.net/archives/2005/09/not_all_publicity_is_good_publicity.html">this article</a> this morning. I am quickly finding 
<a href="http://blogsearch.google.com">Google Blog Search</a> an asset for keeping track of countless forms of information. I am subscribed to search results for Case, all results coming from case.edu, my name, and miscellaneous topics in which I have a keen interest. What I find is very interesting and takes very little effort. I applaud Google for yet another stellar service.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Google Blog Search Makes Searching Public Opinion Easy</title
><link href="http://blog.case.edu/gps10/2005/09/26/google_blog_search_makes_searching_public_opinion_easy"
 /><id
>http://blog.case.edu/gps10/2005/09/26/google_blog_search_makes_searching_public_opinion_easy</id
><published
>2005-09-26T21:13:11Z</published
><updated
>2005-09-26T21:33:52Z</updated
><category term="ATOM" label="ATOM"
 /><category term="Computing" label="Computing"
 /><category term="Computing" label="Computing"
 /><category term="Google" label="Google"
 /><category term="RSS" label="RSS"
 /><category term="syndicated feeds" label="syndicated feeds"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Google released 
<a href="http://blogsearch.google.com">Blog Search</a> a few weeks ago. In short, it is a search performed on 
<a href="http://wiki.case.edu/syndicated_feeds">syndicated feeds</a> on the internet. These feeds are often associated with blogs, but they are also heavily used on informational sites. The feeds themselves can be used to convey a wide range of information. There are two things I really love about Google Blog Search:
<ol>
<li>The content being indexed by Google is highly dynamic and Google updates it frequently. Unlike the regular Google search that indexes results by relevance, the blog search can index results by date retrieved. Not only do you find recent changes, but you can find obscure sources of information.</li>
<li>Search results are available in 
<a href="http://wiki.case.edu/RSS">RSS</a> and 
<a href="http://wiki.case.edu/ATOM">ATOM</a>. This just rocks</li>
</ol>For an institution such as the university that is always cognizant of its public portrayal, Google Blog Search is an invaluable tool. If you are one of these people, you might be interested in the 
<a href="http://blogsearch.google.com/blogsearch?hl=en&amp;utm_source=AdWords&amp;utm_campaign=us-ha-en-blogsearch&amp;utm_term=blog+search&amp;utm_medium=cpc&amp;utm_content=googleblogsearch&amp;q=%22case+western%22&amp;btnG=Search+Blogs&amp;scoring=d">Google Blog Search results for 'Case Western'</a>. Drop the feed of this search result in your favorite aggregator, and you are subscribed to a public opinion pole/news site about Case. It was quite interesting when I saw 
<a href="http://www.discourse.net/archives/2005/09/not_all_publicity_is_good_publicity.html">this article</a> this morning. I am quickly finding 
<a href="http://blogsearch.google.com">Google Blog Search</a> an asset for keeping track of countless forms of information. I am subscribed to search results for Case, all results coming from case.edu, my name, and miscellaneous topics in which I have a keen interest. What I find is very interesting and takes very little effort. I applaud Google for yet another stellar service.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Running a LAMPS Server</title
><link href="http://blog.case.edu/gps10/2005/09/22/running_a_lamps_server"
 /><id
>http://blog.case.edu/gps10/2005/09/22/running_a_lamps_server</id
><published
>2005-09-22T18:10:09Z</published
><updated
>2005-09-22T18:15:33Z</updated
><category term="Computing" label="Computing"
 /><category term="LAMPS" label="LAMPS"
 /><category term="open source" label="open source"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>If anyone out there is interested in an easy way to bring up a 
<a href="http://wiki.case.edu/LAMPS">LAMPS</a> server that is already optimized for the Case environment, check out my 
<a href="http://opensource.case.edu/projects/CaseLAMPS/">Case LAMPS</a> project on 
<a href="http://opensource.case.edu">opensource.case.edu</a>. The project first began when I built the LAMPS server for 
<a href="http://wiki.case.edu/USG">USG</a>. Later, I used the same script to build the server for the Blogs@Case and 
<a href="http://wiki.case.edu/Main_Page">Case Wiki</a> system. Both run very fast and have zero problems with stability.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Case Needs Course Data in LDAP</title
><link href="http://blog.case.edu/gps10/2005/09/15/case_needs_course_data_in_ldap"
 /><id
>http://blog.case.edu/gps10/2005/09/15/case_needs_course_data_in_ldap</id
><published
>2005-09-15T21:37:24Z</published
><updated
>2005-09-15T22:12:31Z</updated
><category term="Case IT" label="Case IT"
 /><category term="Computing" label="Computing"
 /><category term="LDAP" label="LDAP"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Have you ever stopped to think about what could happen if Case's course offerings and course enrollment information were stored in its 
<a href="http://wiki.case.edu/LDAP">LDAP</a> server? Here is a short list:
<ul>
<li>The list of offered courses would be easily available to all
<ul>
<li>Anybody could write a course search tool</li>
<li>Services could automatically provision resources for each course. For example, the Case Wiki could automatically create course pages for every course. The Case Blog system could create group blogs for every course. Oracle Calendar could create groups for each course. The list goes on and on.</li>
<li>Applications needing this information would only need to access LDAP, not worry about parsing ISIS output. Which is easier? Likewise, if someone needed this information, it is much easier to query LDAP than to parse ISIS output.</li>
</ul></li>
<li>Your course enrollment would be easily accessible to services
<ul>
<li>Your Oracle Calendar would automatically subscribe to group calendars of courses to which you are enrolled</li>
<li>You will be automatically subscribed to a group blog for your course</li>
<li>An online course evaluation system could easily see what courses you should be able to review</li>
<li>Services can limit availability to persons enrolled in a specific course. E.g. discussion boards, wikis, software downloads, etc</li>
</ul></li>
<li>Editing your course enrollment would be much simpler. An application that interfaces with LDAP is much easier to write than one that interfaces with ISIS. Change the course registration procedure so that changes to your course enrollment are stored in LDAP and picked up by ISIS, not the other way around. Once this is done, SOLAR becomes obsolete. The student body rejoices.</li>
<li>Access to course information wouldn't be limited to a very select few and thus would eliminate many bottlenecks when obtaining the information. The list of courses offered by Case isn't a secret. Why then can't we publish this list in a format that is easily readable by computers? For those who need course enrollment information, going through the LDAP is much easier than going through the Registrar and parsing whatever awful format in which the information they return is in.</li>
</ul>I'm sure I'm missing a lot of potential uses. Feel free to add a comment to my post and list your ideas.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Are Wiki Engines the Future of Content Management?</title
><link href="http://blog.case.edu/gps10/2005/09/14/are_wiki_engines_the_future_of_content_management"
 /><id
>http://blog.case.edu/gps10/2005/09/14/are_wiki_engines_the_future_of_content_management</id
><published
>2005-09-14T20:09:53Z</published
><updated
>2005-09-14T20:31:27Z</updated
><category term="Computing" label="Computing"
 /><category term="Content Management" label="Content Management"
 /><category term="MediaWiki" label="MediaWiki"
 /><category term="Wiki" label="Wiki"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Wiki software such as MediaWiki, the package that powers 
<a href="http://en.wikipedia.org">WikiPedia</a> and the 
<a href="http://wiki.case.edu/Main_Page">Case Wiki</a>, is very robust and has potential beyond operating wikis. Imagine MediaWiki modified to have granular permissions with adjustable scope. You now have the perfect content management system. The software contains numerous enterprise-class features, such as multi-tier caching and load-balancing. Editing pages is very simple, using an easy-to-learn markup. Also, by using a wiki engine, you would get a full page history and a recent changes list. The differences between wiki software and content management software is very small. With MediaWiki, the only real difference is the lack of a robust permission system and the inability to create infinite levels of structure. If MediaWiki were modified to include these, it would instantly become a free and viable enterprise-class content management system. Anyone looking at shelling out lots of $$$ for a commercial content management system should look at modifying MediaWiki for a fraction of the cost. The results won't be disappointing.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Google Sitemaps Significantly Help Spidering</title
><link href="http://blog.case.edu/gps10/2005/08/15/google_sitemaps_significantly_help_spidering"
 /><id
>http://blog.case.edu/gps10/2005/08/15/google_sitemaps_significantly_help_spidering</id
><published
>2005-08-15T19:10:23Z</published
><updated
>2005-08-15T19:29:58Z</updated
><category term="CaseWiki" label="CaseWiki"
 /><category term="Computing" label="Computing"
 /><category term="Google" label="Google"
 /><category term="MediaWiki" label="MediaWiki"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>A week ago, I registered the 
<a href="http://wiki.case.edu/Main_Page">Case Wiki</a> with 
<a href="https://www.google.com/webmasters/sitemaps/">Google Sitemaps</a> (
<a href="http://mail.wikipedia.org/pipermail/mediawiki-l/2005-August/006254.html">1</a>). Today, I looked at the 
<a href="http://wiki.case.edu/stats/">Case Wiki statistics</a> and was surprised at the difference it makes. Just compare the 
<a href="http://wiki.case.edu/stats/awstats.pl?framename=mainright#robots">Case Wiki robot stats</a> to the 
<a href="http://blog.case.edu/stats/awstats.pl?framename=mainright#robots">Blog@Case robot stats</a>. Even though the Case blog system has more traffic and many more pages, the Google Sitemaps support allowed every single page in the Case Wiki to be indexed overnight. Since the Google Sitemaps XML files also contain metadata about the pages, including their last update time, this means more efficient robot spidering and better search results. With the search engine friendliness of the Case Wiki, I wonder how long it is before articles like 
<a href="http://wiki.case.edu/Department_of_History">Department of History</a> are higher in the search results than the 
<a href="http://www.case.edu/artsci/hsty/">actual site</a>.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Evaluating Single Sign-On Alternatives</title
><link href="http://blog.case.edu/gps10/2005/08/09/evaluating_single_signon_alternatives"
 /><id
>http://blog.case.edu/gps10/2005/08/09/evaluating_single_signon_alternatives</id
><published
>2005-08-09T16:09:56Z</published
><updated
>2005-08-09T17:56:17Z</updated
><category term="CAS" label="CAS"
 /><category term="Computing" label="Computing"
 /><category term="OSSO" label="OSSO"
 /><category term="Oracle" label="Oracle"
 /><category term="SSO" label="SSO"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>In a 
<a href="http://blog.case.edu/gps10/2005/08/09/evaluating_oracle_single_signon">previous post</a>, I raised the need for a replacement single sign-on service for the university and investigated the usage of Oracle's single sign-on product as a viable replacement. The results were discouraging. Therefore, a separate single sign-on product is desired. The first product to grab our attention was 
<a href="http://tp.its.yale.edu/tiki/tiki-index.php?page=CentralAuthenticationService">CAS</a>. What really got our attention was the 
<a href="http://jasigch.princeton.edu:9000/display/CAS/Clients">list of CAS clients</a> as well as the 
<a href="http://jasigch.princeton.edu:9000/display/CAS/CAS+Deployers">list of CAS deployers</a>. Let's evaluate CAS:
<ul>
<li>It is widely used. This means support for the product should be easily available.</li>
<li>It is built using standards. CAS actions are performed using simple HTTP GET and POST requests.</li>
<li>We know what CAS does and can modify it accordingly because the product is open source.</li>
<li>It has plugins for almost every desired usage. The Apache module (for both version 1 and 2) easily install. The modules even work with mod_auth_ldap (I did have to change 4 lines in the source code for this feature, however). If a user doesn't have access to the Apache config, Perl and PHP modules exist to easily integrate your application. For languages without a client yet, designing one is very simple because CAS is built upon standards.</li>
<li>Using CAS requires you to just know the URL of the login server. There is no need for anyone in ITS to configure CAS to allow you to use it.</li>
</ul>So CAS wins big points for being built on standards, easy to use, and easy for ITS to maintain. However, what about the other applications. How do we get the Oracle applications to use CAS? The good news here is that Oracle Single Sign-On can be 
<a href="http://docs.jcu.edu.au/appserver_904_doc/manage.904/b10851/tpsso.htm">integrated with CAS</a>. We could deploy CAS as our primary single sign-on service and Oracle's single sign-on would use CAS to authenticate. In addition, other universities have successfully used CAS as the authentication method for PeopleSoft implementations (our ERP system). Webmail could also be modified to use it. Looking at the big picture, we have two requirements:
<ol>
<li>We must be running Oracle Single Sign-On for the portal</li>
<li>We want to maintain a single sign-on service that is easy for clients to use</li>
</ol>If Oracle Single Sign-On was the only SSO service, #2 would not be true. The requirement of #2 therefore dictates that we operate a separate and primary single sign-on service. CAS seems to fit that requirement perfectly. The only problem left is integrating Oracle Single Sign-On to work with CAS. Until that solution is put in place, users must settle for separately logging into Oracle products; not a big deal considering this is already the case. The advantages of using CAS as our central authentication service are great. The usage barrier for CASifying web sites is so low, that system administrators can easily adopt this solution. Deploying CAS requires a one-time effort by ITS. No intervention is required for new applications to use the service. The solution appears clear. When can we make it official?</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Evaluating Oracle Single Sign-On</title
><link href="http://blog.case.edu/gps10/2005/08/09/evaluating_oracle_single_signon"
 /><id
>http://blog.case.edu/gps10/2005/08/09/evaluating_oracle_single_signon</id
><published
>2005-08-09T15:46:59Z</published
><updated
>2005-08-09T17:13:52Z</updated
><category term="Computing" label="Computing"
 /><category term="OSSO" label="OSSO"
 /><category term="Oracle" label="Oracle"
 /><category term="SSO" label="SSO"
 /><category term="mod_osso" label="mod_osso"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Many of you know about 
<a href="https://login.case.edu">login.case.edu</a>. It makes your lives much easier because now you only have to enter your password once for numerous web services. However, there is a problem with the service: it is too complicated. It is not too complicated for the average user, but for the people who implement it. Just look at 
<a href="http://wiki.case.edu/Pubcookie_Configuration">the hoops you have to jump through</a> to get it working on your own server. What's more is that it relies on a web server module (not everybody has access to the web server config files) and requires somebody in ITS to manually do work every time a new client wishes to use it. What is needed is an alternative. Well, we are already running an Oracle Single Sign-On product, so let's use that! OK, let's evaluate the Oracle product.
<ol>
<li>We are using it because it is required by the 
<a href="http://my.case.edu">portal</a>.</li>
<li>It requires manual intervention every time a new client wishes to use it. Isn't this a reason why we are investigating alternative?</li>
<li>The Oracle products easily integrate with it. Hooray! No more separate logins for the portal and the calendar.</li>
<li>Writing external programs to authenticate against it requires the use of a C or Java SDK. (I can hear the screams of agony now).</li>
<li>The module mod_osso appears to only be available for Oracle's Application Server. Does it work with IIS? No. Does it work with your standalone Apache? I don't know either. Judging from a 
<a href="http://www.google.com/search?rls=en&amp;q=mod_osso+apache2&amp;ie=UTF-8&amp;oe=UTF-8">Google search</a>, I'd say it isn't promising. Most importantly, does it work with mod_auth_ldap? Well, we don't know. If it doesn't, there is nothing we can do because the module is closed source.</li>
</ol>In summary, we are being forced to use Oracle Single Sign-On, but it works well with the Oracle Applications. No matter what we decide to do, we will have to use this product. If we decide to make it the only SSO service for the university, a significant amount of effort would be required for every new application deployed to use it. Would system administrators make this effort to configure it, or would they take the easy way out and just resort to the tried and true LDAP authentication? Also, any department that uses IIS to host web applications would be unable to use the service. Do we really want to deploy a single sign-on service that only a subset of the university can use? In my next post, I will explore alternatives to Oracle Single Sign-On and how they could integrate with the Oracle applications.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
><entry
><title
>Java is Not a Web Application Language</title
><link href="http://blog.case.edu/gps10/2005/08/05/java_is_not_a_web_application_language"
 /><id
>http://blog.case.edu/gps10/2005/08/05/java_is_not_a_web_application_language</id
><published
>2005-08-05T14:48:54Z</published
><updated
>2005-08-05T15:07:05Z</updated
><category term="Computing" label="Computing"
 /><category term="Java" label="Java"
 /><category term="PHP" label="PHP"
 /><category term="Tomcat" label="Tomcat"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>It seems that everyone is on the Java bandwagon nowadays. Along with XML, it is something that every project coordinator wants to use in his product, no matter what the product may be. Some applications should NOT be written in Java. Web applications are one class where this holds true. After writing a web application in C++, I said there is no worse popular programming language for a web application. When Java arrived and was herralded as the language to end all languages, I never thought it would challenge C++ for this honor. Well, it has. After spending the whole day yesterday bringing up a Tomcat installation and attempting to install CAS, an alternate single sign-on to possibly replace our current Pubcookie implementation, I am sold. Java is great for multi-platform portability, but for web applications, I'll stick to my runtime interpretted languages such as PHP, Python, and Perl. The benefits that Java offers for the average web application are few and far between. Why would I write a web application (something that is highly likely to require change in a production environment) in a compiled language? Runtime interpretted languages have the benefit of being instantly changed without recompiling and performance is barely slower. Their memory footprint is significantly less. What's more is that many of these languages are either designed specificially for web development or have easy-to-use modules for web development. Writing a web application in Java is just overengineering the solution. Java is great for many applications, don't get me wrong. But for the average web application (one that isn't your multi-million dollar corporate product), Java should be avoided at all cost. Stick to an interpretted language. The clients will thank you in the end.</div
></content
><author
><name
>Gregory Szorc</name
><email
>gregory.szorc@case.edu</email
><uri
>http://blog.case.edu/gps10</uri
></author
></entry
></feed
>