Two aspects of the variety of formats of presentation of the Unit 6 material which struck me as interesting had to do with the podcasts.
The first aspect had to do with my expectations about the accessibility of content with respect to a delivery format. Prior to viewing the Harvard Computer Science Podcast, my expectation of the podcast format was that of exclusively audio content delivery. Given this expectation, I was skeptical that the information content could be effectively conveyed to me in audio-only format. I was relieved to discover my notions of podcasting to be dated, and thought the actual audio-video presentation of the Harvard Computer Science Podcasts to be highly effective. However, I began to wonder why this should be the case. Because overall, the video component of the podcast did not substantively contribute additional quantitative information absent from the audio. Much of the video content was an image of a professor delivering a lecture. The same amount quantifiable content would have been delivered if the format were solely audio, but I'm sure I would not have judged it to be an effective presentation. My guess is the distinction speaks to a certain vague subjective factor in effective content delivery. I think much of this has to do with content user expectations. I expect to see a lecture if I am listening to a lecture. Watching the video of the lecture added something to the audio information which I think was mainly of a subjective quality. But the addition, at least for me, was very important. But on the other hand, maybe I'm making too much of this. I do listen to radio broadcasts of baseball games.
The second aspect had to do with the RSS component of podcast format, and the effect of this technology on my understanding of the models of networking architecture. Specifically, what is the designation of an architectural component which, to me, is neither precisely a client nor a server? The content of the Harvard Computer Science Podcasts is hosted by the content creators, presumably by servers of Harvard. But users request this content not from Harvard servers, but from iTunes. So my question is, what is the name for functional role of iTunes in this instance? Maybe I am making too much of this, but I think what it adds to the simple client-server model is interesting. This is the second time I have had the impression that RSS creates interesting effects with networking architecture. At the Computers in Libraries Conference in 2007, I listened to a presentation by a librarian at the Rand Corporation. He was using RSS in an innovative way, providing a greater degree of freedom for
I would say the Unit 6 material is relatively "deep," and the variety of presentations of the same repeated content was helpful. For instance, I found the Warriors of the Net animation to be very helpful for me to conceptualize TCP/IP. The same material, for me, was effectively reinforced in detail in Nemeth's Linux Administration Handbook. I found the Wikipedia articles on local area networks to be very helpful gaining a conceptual understanding of the applied assignment.
