<?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: web applications</title
><link rel="self" href="http://blog.case.edu/topics/web%20applications"
 /><id
>http://blog.case.edu/topics/web%20applications</id
><category term="web applications" label="web applications"
 /><link rel="related" href="http://blog.case.edu/topics/open%20source%20tools" title="open source tools"
 /><link rel="related" href="http://blog.case.edu/topics/technology" title="technology"
 /><link rel="related" href="http://blog.case.edu/topics/open%20source" title="open source"
 /><link rel="related" href="http://blog.case.edu/topics/messaging" title="messaging"
 /><link rel="related" href="http://blog.case.edu/topics/calendaring" title="calendaring"
 /><link rel="related" href="http://blog.case.edu/topics/voip" title="voip"
 /><contributor
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></contributor
><updated
>2008-12-08T20:56:40Z</updated
><entry
><title
>ITS Status meets Twitter.</title
><link href="http://blog.case.edu/sdh7/2008/12/08/its_status_meets_twitter"
 /><id
>http://blog.case.edu/sdh7/2008/12/08/its_status_meets_twitter</id
><published
>2008-12-08T20:34:46Z</published
><updated
>2008-12-08T20:56:40Z</updated
><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Last year, we did some experiments using 
<a href="http://www.twitter.com">Twitter</a> as an internal notification tool. I had whipped up some code to tie it to Rover, which was the internal network status tool that we used until October 2007. After Rover was decommissioned, the Twitter account went dormant. Last week, I took it out of mothballs, 
<a href="http://twitter.com/CaseITSStatus">changed the name</a>, made it public, and connected it to the 
<a href="http://blog.case.edu/its-status/">ITS Status blog</a> using 
<a href="http://twitterfeed.com/">Twitterfeed</a>. Who knows, maybe I can convince some of the other engineers to provide updates as well... So, if you want the latest ITS status updates on Twitter, follow 
<a href="http://twitter.com/CaseITSStatus">CaseITSStatus</a>.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>A simpler time tracking</title
><link href="http://blog.case.edu/sdh7/2008/04/23/a_simpler_time_tracking"
 /><id
>http://blog.case.edu/sdh7/2008/04/23/a_simpler_time_tracking</id
><published
>2008-04-23T19:44:03Z</published
><updated
>2008-04-23T22:24:31Z</updated
><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a href="http://www.37signals.com/svn/posts/976-a-peek-at-inout-an-internal-app-at-37signals">37Signals In/Out</a> - Something along these lines (but not this exact thing) seems like a much better way to do time tracking than what we're using now.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>A change to Docshare</title
><link href="http://blog.case.edu/sdh7/2008/01/04/a_change_to_docshare"
 /><id
>http://blog.case.edu/sdh7/2008/01/04/a_change_to_docshare</id
><published
>2008-01-04T19:51:13Z</published
><updated
>2008-01-07T16:02:24Z</updated
><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>Due to some misconfigurations, fixes to those misconfigurations, and fixes to the fixes, it's become necessary in certain cases to use a slightly different URL to access WebDAV on Docshare. For your personal folder(s), you should still be able to use the URL: https://docshare.case.edu/&lt;uid&gt;/ However, for users you've been given permission to access their folder(s), or if you're a non-admin user of an organizational folder, you'll need to use a URL something like: https://docshare.case.edu/dav/&lt;folder&gt;/ This has to do with the way that VTFileman creates the Apache .htaccess and .davaccess files.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>A brief presentation about Case IM and Docshare</title
><link href="http://blog.case.edu/sdh7/2007/09/21/a_brief_presentation_about_case_im_and_docshare"
 /><id
>http://blog.case.edu/sdh7/2007/09/21/a_brief_presentation_about_case_im_and_docshare</id
><published
>2007-09-21T16:59:22Z</published
><updated
>2007-09-21T17:15:31Z</updated
><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>This morning, I gave a brief demonstration of 
<a href="http://docshare.case.edu/">Docshare</a> and Case IM to the 
<a href="http://wiki.case.edu/Information_Technology_Services_Planning_and_Advisory_Committee">ITS Planning and Advisory Committee</a>. I made some slides with the 
<a href="http://googleblog.blogspot.com/2007/09/our-feature-presentation.html">new presentations tool</a> in 
<a href="http://wiki.case.edu/GoogleApps">Google Apps</a>. I've just uploaded a slightly enhanced version of them 
<a href="http://docshare.case.edu/sdh7/presentations/im-docshare/">on Docshare</a>, so check it out.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>Bedework Calendar</title
><link href="http://blog.case.edu/sdh7/2006/08/07/bedework_calendar"
 /><id
>http://blog.case.edu/sdh7/2006/08/07/bedework_calendar</id
><published
>2006-08-07T20:01:51Z</published
><updated
>2006-08-07T20:46:42Z</updated
><category term="Calendaring" label="Calendaring"
 /><category term="Open Source Tools" label="Open Source Tools"
 /><category term="Web Applications" label="Web Applications"
 /><category term="open source" label="open source"
 /><category term="technology" label="technology"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I first looked at 
<a href="http://www.bedework.org">Bedework</a> a few months ago, and it seemed pretty primitive to me - just a fancy event calendar. I just looked at it again and it looks like they've made a lot of progress, adding personal calendars with CalDAV access, RSS feeds and other features. It's not quite in a position where we would want to adopt it, I think, since I can't figure out any way to invite people to my meetings, and setting up authentication outside of the built-in database consists of "configure Tomcat to talk to LDAP or CAS". It also seems a little slow to me, but I am just running the quickstart version with embedded HSQLDB, and it's dumping tons of debugging output on the console, so those two factors may have something to do with that.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>GVC.Sitemaker</title
><link href="http://blog.case.edu/sdh7/2006/08/03/gvcsitemaker"
 /><id
>http://blog.case.edu/sdh7/2006/08/03/gvcsitemaker</id
><published
>2006-08-03T18:30:32Z</published
><updated
>2006-08-03T18:41:28Z</updated
><category term="Open Source Tools" label="Open Source Tools"
 /><category term="Web Applications" label="Web Applications"
 /><category term="technology" label="technology"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a href="http://www.gvcsitemaker.com/">GVC.Sitemaker</a>, the open-source version of the 
<a href="http://www.campus-technology.com/article.asp?id=18938">University of Michigan's UM.Sitemaker</a>. It's not quite a 
<a href="http://blog.case.edu/jms18/2006/02/01/three_wanted_its_services_wiki_farm">wiki</a> 
<a href="http://blog.case.edu/gps10/2006/03/24/thoughts_on_establishing_a_wiki_farm">farm</a>, but it is pretty interesting looking.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>WebObjects</title
><link href="http://blog.case.edu/sdh7/2006/03/07/webobjects"
 /><id
>http://blog.case.edu/sdh7/2006/03/07/webobjects</id
><published
>2006-03-07T21:12:06Z</published
><updated
>2006-03-07T22:11:22Z</updated
><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>I've been toying with Apple's 
<a href="http://www.apple.com/webobjects/">WebObjects</a> a bit lately - partly due to an on-the-horizon project that's written with it, and partly due to the fact that I've wanted to try it out since the days when it cost $50K, required coding in Objective-C and ran on NeXTSTEP. Of course, now it's pretty much free, requires coding in Java, and runs on Mac OS X (but with a little luck and effort, applications are deployable on most any J2EE container). It's pretty interesting so far. You can deploy (rudimentary) applications with very little code - I wrote an insanely simple app that copied from one textfield to another, and it only required writing one line of Java. There's also the "Direct To Web" deployment option, which, given an EOModel (more on that later), will generate an entire skeletal application for you much like 
<a href="http://www.rubyonrails.org/">Ruby on Rails</a>. Lastly, there's a "Direct to Web Services" option, which can build SOAP Web Services (using 
<a href="http://ws.apache.org/axis/">Apache Axis</a>, apparently - I haven't tried the D2WS option yet) based on your model. EOModeler (one of the applications in WebObjects), is really interesting. It can scan the schema of a JDBC or JNDI(i.e. LDAP) store and allow you to graphically connect together the relationships between your tables, and then (optionally) generate the necessary SQL or Java code to re-create the database again (for, say, an installer). There are some things I don't like - check out the URLs for products at 
<a href="http://store.apple.com">store.apple.com</a> - they're horrendously long, and not easily bookmarkable - there's a session ID built into the URL, though with a little 
<a href="http://rentzsch.com/woWebLog/httpdConfChanges">mod_rewrite magic</a>, you might be able to cope with them a little better. As far as I've read, the closest to WebObjects in the regular J2EE world would be 
<a href="http://objectstyle.org/cayenne/">Cayenne</a> (for object modeling) and 
<a href="http://jakarta.apache.org/tapestry/index.html">Tapestry</a> (as the web framework). Outside of J2EE, it's similar to a lot of the MVC web frameworks coming out, such as 
<a href="http://www.rubyonrails.org/">Rails</a> or 
<a href="http://catalyst.perl.org/">Catalyst</a>.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>Open Source Portfolios</title
><link href="http://blog.case.edu/sdh7/2006/02/15/open_source_portfolios"
 /><id
>http://blog.case.edu/sdh7/2006/02/15/open_source_portfolios</id
><published
>2006-02-15T17:40:26Z</published
><updated
>2006-02-24T19:05:54Z</updated
><category term="Open Source Tools" label="Open Source Tools"
 /><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<a href="http://www.osportfolio.org/">Open-Source Portfolios</a> I've started playing with this just a tiny bit and it seems pretty nice. It may require some slightly more serious hacking to integrate with LDAP and the like, but it's definitely interesting.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
><entry
><title
>Unified Messaging and Mail forwarding</title
><link href="http://blog.case.edu/sdh7/2006/02/13/unified_messaging_and_mail_forwarding"
 /><id
>http://blog.case.edu/sdh7/2006/02/13/unified_messaging_and_mail_forwarding</id
><published
>2006-02-13T21:24:18Z</published
><updated
>2006-02-22T18:57:15Z</updated
><category term="Messaging" label="Messaging"
 /><category term="VOIP" label="VOIP"
 /><category term="Web Applications" label="Web Applications"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>So, many users have been converted over to Unified Messaging from the old DirecTalk voicemail system. If you're one of them, you may have noticed some peculiar things about how the system works: 1. You actually get two copies of each voicemail message - one in your INBOX and one in a separate folder called "UM-Messages". This is in order to be useful to the two different camps of users we have on campus (POP users and IMAP/Webmail users), and the two different methods of message access (via e-mail and via telephone, or "TUI"). Since we try to be everything to everyone, we set up what's known as a "System-level 
<a href="http://www.faqs.org/rfcs/rfc3028.html">Sieve</a> filter" that checks each incoming message and does the special delivery if it's a voicemail message. 2. Mail forwarding causes some strange behavior, or does things you don't want it to. When mail is forwarded, the UM-Messages copy doesn't occur, so you don't get to check your mail via the TUI, only through your forwarded mail. We're looking into some more automatic workarounds for #1 for power users (i.e. those who only want one copy of the message or the other, and not both). Stay tuned... To solve #2, Joel Kraft actually went to the trouble figuring out enough to write some of his own 
<a href="http://www.faqs.org/rfcs/rfc3028.html">Sieve</a> templates to add into Delegated Administrator. They did require a couple of minor edits before they were working 100% correctly, but they're in there now. Here's how to use them: 1. Go to 
<a href="https://ims-web.case.edu:8088/nda/default/en/login.htm">Delegated Administrator</a> and log in 2. If you are currently forwarding mail, turn that off, and turn mailbox delivery back on- it sounds counter-intuitive, but trust me on this one. 3. Now go to the "Set Mail Filters" view. (Unfortunately, this tends to render weird in Firefox, but looks fine in IE or Safari). From the menu, select "Forward Everything (Copy Voicemail). Make up a name for the rule, and enter the e-mail address you want to forward to. 4. Click OK, and then save your rules. You're done.</div
></content
><author
><name
>Samuel Harmon</name
><email
>samuel.harmon@case.edu</email
><uri
>http://blog.case.edu/sdh7</uri
></author
></entry
></feed
>