<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
   <channel>
      <title>Joy&apos;s Blog</title>
      <link>http://learningremix.net/w2007integ/jvaradar/</link>
      <description>Joy&apos;s  Blog</description>
      <language>en</language>
      <copyright>Copyright 2007</copyright>
      <lastBuildDate>Sun, 22 Apr 2007 11:34:41 -0500</lastBuildDate>
      <generator>http://www.sixapart.com/movabletype/</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <item>
         <title>My last blog post</title>
         <description>Here is my last post since I&apos;ll be hitting the magic number after this post. I wanted to share my opinions about this course in this post.

First of all, it was a great learning experience. I&apos;ve learned a lot thro&apos; this course. Before the course started, I&apos;ve just heard about AJAX. Now, I&apos;ve gained good knowledge about working in AJAX. Thro&apos; the mini projects and group project, we were able to learn how to do programming in AJAX and gained hands-on experience by applying it in our projects.

I&apos;ve to mention about the weekly presentations. Earlier, I was never comfortable while giving presentations. I cannot speak in a crowd. But now I&apos;ve gained confidence to speak in front of everyone. That&apos;s an important skill to be developed for business students. 

The blog posts-very informative and educative. Even though, at times I felt pressured to keep up to the required number, it was fun. It has created a habit of looking for information. I guess it&apos;s a good habit to continue to seek knowledge.

Thanks Professor for providing us a different learning experience.</description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/my_last_blog_post.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/my_last_blog_post.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">Blog</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">final</category>
        
         <pubDate>Sun, 22 Apr 2007 11:34:41 -0500</pubDate>
      </item>
            <item>
         <title>Review of ISA site</title>
         <description>Great improvement and refinement after Iteration 2. The appearance has changed a lot after your second iteration. You guys must have worked really hard work to achieve this. Here are my comments on your site.

Utilization of lot of API&apos;s. Must&apos;ve been really challenging to integrate all of them.
I like the news on the side panel. It gives a really neat appearance.
Taking the buttons out of the map and displaying it on the side, gives lot of space to display the map.
The search and save option is a good feature. If it can be saved like &quot;MyFavoritePlaces.org&quot; it&apos;ll add more value to your site.

Overall great job guys! Good luck.
</description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/review_of_isa_site.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/review_of_isa_site.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">ISA Site</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">iteration 3Review</category>
        
         <pubDate>Sun, 22 Apr 2007 11:27:17 -0500</pubDate>
      </item>
            <item>
         <title>Iteration 3 by AJACS team</title>
         <description><![CDATA[Here is the link for iteration 3 of our Virtual India project.

<a href="http://people.emich.edu/amodukur/Final%20project/home.html"><u>Virtual India</u></a>

AJACS Team
]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/iteration_3_by_ajacs_team.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/iteration_3_by_ajacs_team.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">AJACS</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">Iteration3site</category>
        
         <pubDate>Wed, 18 Apr 2007 18:28:02 -0500</pubDate>
      </item>
            <item>
         <title>Question about Iteration 3</title>
         <description>At the beginning of last week&apos;s class, Bud said he&apos;ll post some instructions in his blog post regarding today&apos;s iteration. Is it so or have I missed something since I left early last week?

Is there going to be a review for today&apos;s iteration. Do we need to tag it with iteration 3 or something as we used to do before?

If some knows about this please reply.

</description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/question_about_iteration_3.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/question_about_iteration_3.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">iteration 3</category>
        
         <pubDate>Wed, 18 Apr 2007 13:33:05 -0500</pubDate>
      </item>
            <item>
         <title>DOM Tutorials</title>
         <description><![CDATA[I was browsing for some DOM tutorials at google. I found this site <a href="http://www.topxml.com/dom/default.asp">http://www.topxml.com/dom/default.asp</a> where you can learn everything about XML DOM and how to make use of it in your applications. It serves as a good reference with source codes, examples, downloads etc. I hope it will be useful for students who are introduced to DOM]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/dom_tutorials_1.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/dom_tutorials_1.shtml</guid>
        
        
         <pubDate>Thu, 05 Apr 2007 15:15:32 -0500</pubDate>
      </item>
            <item>
         <title>Speeding up Ajax with JSON</title>
         <description><![CDATA[I found this article about how to speed up your ajax application with Ajax. Here it is!

Speed is everything when it comes to online applications. Users hate to sit and wait, especially the experienced ones. A few seconds pass and they start to think something’s broken. Knowing this, optimizing everything you can on your application can mean the difference between someone leaving or sticking around to explore the site more. One method for enhancing the speed in your app is described <a href="http://www.developer.com/lang/jscript/article.php/3596836"><u>here on Builder.com</u></a> - using JSON to speed up your Ajax script’s connection between it and the server.

    XML is the standard way to interchange data, but it’s often not the best way. Although XML can add structure and metadata to data, it does so in an overly verbose way. XML also has a fairly complex syntax, requiring a non-trivial parser to attack it. In JavaScript, XML must be parsed into a DOM tree to be used. And, once you’ve constructed the DOM tree, you still have to pilot through it to create corresponding JavaScript objects or otherwise use the XML data in your client-side Web application.

   The <a href="http://www.developer.com/lang/jscript/article.php/3596836"><u>article</u></a> introduces JSON to the reader, offering a comparison with a matching XML structure. Their point of view is that XML is great for marking up data, but JSON is meant for the speed of data exchange. There’s an example provided of the difference between the same request done in both XML and JSON, with the JSON seeming to be the simpler. The article finished off with a look at how reliable JSON is for your application, and some mention of life on the other side - the server-side functionality. ]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/speeding_up_ajax_with_json.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/speeding_up_ajax_with_json.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">ajax</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">JSON</category>
        
         <pubDate>Thu, 05 Apr 2007 12:18:13 -0500</pubDate>
      </item>
            <item>
         <title>Shaping the future of secure Ajax mashups</title>
         <description><![CDATA[Current Web browsers weren't designed to easily and securely get content from multiple sources into one page. This <a href="http://www-128.ibm.com/developerworks/library/x-securemashups/"><u>article</u></a> discusses about how developers have stretched the available tools to fit the task and how doing so has put strain on the resulting applications with respect to security and scalability. Also, several browser improvements being proposed to remedy the situation has been discussed that will bring Web development beyond this hurdle to a new level of interoperability.

Dynamic HTML (DHTML) was not initially used in combination with dynamically retrieved content. Both the presentation and data elements of a dynamic Web page were delivered together along with scripts to manipulate them. Data flow was synchronous with page reload.

Consequently, developers who wished to build the kind of hybrid Web application that we now call a mashup had to take the available technology and find ways to stretch it to fit their needs. Two approaches were taken to allow the browser to retrieve content without reloading the page: embedding an external transport mechanism and using browser-native objects to perform transport duties.

An early solution was Microsoft's Remote Scripting, which used a Java™ applet that exchanged XML-formatted messages with server-side components. This approach quickly became unwieldy because of vendor squabbles as well as Java Virtual Machine (JVM) and security model differences.

Microsoft later built the XMLHttpRequest (XHR) object, whose designers had the expectation that it would be used only with Microsoft® Outlook® Web Access (OWA). The object was initially available only to Windows® Internet Explorer® users and subsequently not widely used until years later, when Mozilla and Safari adopted it. Originally an external Microsoft ActiveX® object, current implementations are native objects within the browser. Despite its name, the XHR object can transfer data in any format and is not limited to valid XML.

Because of the problems and dependencies associated with external transport mechanisms, the internet development community has collaborated in the discovery and development of several browser-native remote calling methods.

    * Using a hidden iframe element to load external content: The iframe is then accessed through the DOM to extract the content from the document it has loaded. You can specify any parameters in the URL querystring or dynamically create a form that posts to the service with the iframe as a target. This method is compatible across a wide range of both current and older browsers.
    * Using an img element to send requests for content: The server performs its task using the parameters from the URL's querystring, and then returns encoded content in a cookie. This method is limited in the amount of data that can be easily communicated, because both querystring and cookies are limited in size.
    * Dynamically creating a script element in the DOM of the current page: Upon loading, code that the server supplies is immediately executed. The server uses parameters from the URL querystring.

Potential Solutions

 A more recently developed content-retrieval technique employs communication between a page's script and a hidden iframe through its src URL's fragment identifier (the part of the URL that comes after the # sign). Scripts in the parent page and embedded iframe can set each other's fragment identifiers despite coming from different origins. An agreed-upon communication protocol is maintained between the scripts, driven by JavaScript timers that periodically fire routines to check for changes in the fragment identifier.
         Because the scripts must know each other's addresses and they must collaborate between themselves to agree on a protocol, trust is ensured. Because any server interaction is local to each component and separate from the inter-script communication, cookies are not exposed.

<strong>Long term</strong>
          Browser manufacturers and the development community are currently discussing several potential ways to modify elements of the browser environment to make it purpose-built for Ajax mashups. The Web Hypertext Application Technology Working Group (WHATWG) has a proposal in section 7.3 of its Web Applications 1.0 Working Draft for a mechanism called Cross Document Messaging. The Opera browser already implements this feature. It specifies a method of collaborative communication between DOM objects from different domains that allow the receiver of a message to choose which messages to respond to based on their origin.

Here are some proposals:
1. Cross-site extensions to the existing XMLHttpRequest object. The proposal consists of several modifications to the way requests are made, including restrictions on header control and an access-control mechanism.

2. Another proposal is JSON, a data-interchange format that is widely used in Ajax applications, primarily because it is readily parsable by JavaScript and less verbose than XML. ]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/shaping_the_future_of_secure_ajax_mashups.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/shaping_the_future_of_secure_ajax_mashups.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">ajax</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">mashups</category>
        
         <pubDate>Wed, 04 Apr 2007 08:16:20 -0500</pubDate>
      </item>
            <item>
         <title>AJACS  uses Yahoo Weather instead of Weatherbug</title>
         <description>Here is the update on our project.

One of the common comments/weaknesses during iteration 2 review was that, the exact weather is not being displayed for the city chosen from the drop down box. As we discussed in class, the issue was with weatherbug. They update the weather information for international destinations once in 3-6 hours. Meanwhile, if we search weather for a particular destination, it&apos;ll pull the available weather from any station at that moment irrespective of that location. 

To resolve this issue, we tried to display the weather using Yahoo Weather instead of Weatherbug API  and we were successful. It works fine now. We&apos;ll show it in class during the presentation.

AJACS team.</description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/04/ajacs_uses_yahoo_weather_instead_of_weatherbug.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/04/ajacs_uses_yahoo_weather_instead_of_weatherbug.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">AJACS</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">projectupdate</category>
        
         <pubDate>Sun, 01 Apr 2007 13:37:53 -0500</pubDate>
      </item>
            <item>
         <title>JSON: The Fat-free alternative to XML</title>
         <description><![CDATA[ XML provides two enormous advantages as a data representation language:
   1. It is text-based.
   2. It is position-independent.
But XML is not well suited to data-interchange. XML has big problems as a data-interchange format, but the disadvantages are compensated for by the benefits of interoperability and openness.

JSON has all the advantages as XML, but is much better suited to data-interchange.JSON promises the same benefits of interoperability and openness, but without the disadvantages. Here is a comparison between XML and JSON.

Here are some comparisons between XML and JSON.
<strong>Simplicity</strong>
XML is simpler than SGML, but JSON is much simpler than XML. JSON has a much smaller grammar and maps more directly onto the data structures used in modern programming languages.

<strong>Extensibility</strong>
JSON is not extensible because it does not need to be. JSON is not a document markup language, so it is not necessary to define new tags or attributes to represent data in it.

<strong>Interoperability</strong>
JSON has the same interoperability potential as XML.

<strong>Openness</strong>
JSON is at least as open as XML, perhaps more so because it is not in the center of corporate/political standardization struggles.

Here is a link to the <a href="http://www.json.org/xml.html"><u>article</u></a>




]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/json_the_fatfree_alternative_to_xml.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/json_the_fatfree_alternative_to_xml.shtml</guid>
        
        
         <pubDate>Fri, 30 Mar 2007 07:06:03 -0500</pubDate>
      </item>
            <item>
         <title>Re: Error when adding links to posts</title>
         <description><![CDATA[This is in response to  Linda's post regarding error when adding links to posts. I had the same error. Bud has posted regarding this issue. Have a look at <a href="http://learningremix.net/w2007integ/fgibson/2007/03/fixing_the_posting_error.shtml"><u>"Fixing the post error"</u></a>

]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/re_error_when_adding_links_to_posts.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/re_error_when_adding_links_to_posts.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">Fixing the post error</category>
        
         <pubDate>Tue, 27 Mar 2007 09:55:02 -0500</pubDate>
      </item>
            <item>
         <title>Re: Error about publishing</title>
         <description><![CDATA[I didn't check Bud's post about fixing the error. I had a look at <a href="http://learningremix.net/w2007integ/fgibson/"><u>Bud's post</u></a> and fixed the problem.

]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/re_error_about_publishing.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/re_error_about_publishing.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">blogpost</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">error</category>
        
         <pubDate>Mon, 26 Mar 2007 20:38:45 -0500</pubDate>
      </item>
            <item>
         <title>Error while creating blog post</title>
         <description>I was trying to create a new blog post and save it. When I pressed the save button, I got an internal  server error and was asked to contact fgibson@pair.com for fixing the error. But the blog post has been displayed thrice at learning remix.
Does anyone have faced this?</description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/error_while_creating_blog_post_1.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/error_while_creating_blog_post_1.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">blogpost</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">error</category>
        
         <pubDate>Mon, 26 Mar 2007 20:32:43 -0500</pubDate>
      </item>
            <item>
         <title>Google Personal Homepage Gets Skinnable</title>
         <description><![CDATA[I read about this blog post about Google's personalized home pages with the new addition of dynamic themes to it.  Dynamic themes have a remarkably modest effect of color theme on the gadgets. From the post,

      "Mostly, what they do is add a customizable graphical bar around the Google log--a sort of offshoot and expansion of the holiday logos that have been part of Google ever since there's been a Google. In other words, a themed homepage has a dash more personality than an unthemed one, but both retain an essentially Googley look and feel."

When the commenter 'Harry McCracken' tried it out, there was a change in display from login to login. The season landscape displays the snow man sitting in the dark(since it's winter and night time). All the ones I've seen look pretty slick and tasteful. To read the entire article <a href="http://blogs.pcworld.com/techlog/archives/003904.html"><u>click here</u></a>.]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable_2.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable_2.shtml</guid>
        
                  <category domain="http://www.sixapart.com/ns/types#tag">dynamic themes</category>
                  <category domain="http://www.sixapart.com/ns/types#tag">google</category>
        
         <pubDate>Mon, 26 Mar 2007 20:30:01 -0500</pubDate>
      </item>
            <item>
         <title>Google Personal Homepage Gets Skinnable</title>
         <description><![CDATA[I read about this blog post about Google's personalized home pages with the new addition of dynamic themes to it.  Dynamic themes have a remarkably modest effect of color theme on the gadgets. From the post,

      "Mostly, what they do is add a customizable graphical bar around the Google log--a sort of offshoot and expansion of the holiday logos that have been part of Google ever since there's been a Google. In other words, a themed homepage has a dash more personality than an unthemed one, but both retain an essentially Googley look and feel."

When the commenter 'Harry McCracken' tried it out, there was a change in display from login to login. The season landscape displays the snow man sitting in the dark(since it's winter and night time). All the ones I've seen look pretty slick and tasteful. To read the entire article <a href="http://blogs.pcworld.com/techlog/archives/003904.html"><u>click here</u></a>.

 ]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable.shtml</guid>
        
        
         <pubDate>Mon, 26 Mar 2007 20:11:37 -0500</pubDate>
      </item>
            <item>
         <title>Google Personal Homepage Gets Skinnable</title>
         <description><![CDATA[I read about this blog post about Google's personalized home pages with the new addition of dynamic themes to it.  Dynamic themes have a remarkably modest effect of color theme on the gadgets. From the post,

      "Mostly, what they do is add a customizable graphical bar around the Google log--a sort of offshoot and expansion of the holiday logos that have been part of Google ever since there's been a Google. In other words, a themed homepage has a dash more personality than an unthemed one, but both retain an essentially Googley look and feel."

When the commenter 'Harry McCracken' tried it out, there was a change in display from login to login. The season landscape displays the snow man sitting in the dark(since it's winter and night time). All the ones I've seen look pretty slick and tasteful. To read the entire article <a href="http://blogs.pcworld.com/techlog/archives/003904.html"><u>click here</u></a>.

 ]]></description>
         <link>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable_1.shtml</link>
         <guid>http://learningremix.net/w2007integ/jvaradar/2007/03/google_personal_homepage_gets_skinnable_1.shtml</guid>
        
        
         <pubDate>Mon, 26 Mar 2007 20:11:37 -0500</pubDate>
      </item>
      
   </channel>
</rss>
