<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Pos Malaysia shipping quote &#8211; part 2</title>
	<atom:link href="http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/</link>
	<description>Working nights with the thief of time</description>
	<lastBuildDate>Sun, 01 Jan 2012 17:42:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Sean</title>
		<link>http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/comment-page-1/#comment-3482</link>
		<dc:creator>Sean</dc:creator>
		<pubDate>Mon, 13 Dec 2010 09:42:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lolyco.com/sean/?p=787#comment-3482</guid>
		<description>It&#039;s a good question - the answer is &#039;no&#039;. The answer is only no because none of the e-commerce projects I&#039;ve used in the past handled product volume in any meaningful way. The way I store data from the shipping agents would make it easy to add in a volume parameter, it might just take a bit of to-and-fro to establish the &#039;best compromise&#039; for an API. I&#039;m open to suggestions of how to build it in.

I&#039;ve done a little bit of work on the shipping API in the last few days - a demo of a ZenCart module for someone. The basic API is an URL of the shape &quot;WEIGHT-to-DESTINATION-ex-ORIGIN.CONTENTTYPE&quot;. It would be easy to provide an URL like &quot;WEIGHT-vol-LENGTH-WIDTH-HEIGHT-to-DESTINATION-ex-ORIGIN.CONTENTTYPE&quot;. Let me know if you&#039;d like to see a demo and I&#039;ll work something out.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a good question &#8211; the answer is &#8216;no&#8217;. The answer is only no because none of the e-commerce projects I&#8217;ve used in the past handled product volume in any meaningful way. The way I store data from the shipping agents would make it easy to add in a volume parameter, it might just take a bit of to-and-fro to establish the &#8216;best compromise&#8217; for an API. I&#8217;m open to suggestions of how to build it in.</p>
<p>I&#8217;ve done a little bit of work on the shipping API in the last few days &#8211; a demo of a ZenCart module for someone. The basic API is an URL of the shape &#8220;WEIGHT-to-DESTINATION-ex-ORIGIN.CONTENTTYPE&#8221;. It would be easy to provide an URL like &#8220;WEIGHT-vol-LENGTH-WIDTH-HEIGHT-to-DESTINATION-ex-ORIGIN.CONTENTTYPE&#8221;. Let me know if you&#8217;d like to see a demo and I&#8217;ll work something out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian</title>
		<link>http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/comment-page-1/#comment-3481</link>
		<dc:creator>Brian</dc:creator>
		<pubDate>Mon, 13 Dec 2010 09:18:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lolyco.com/sean/?p=787#comment-3481</guid>
		<description>Hi sean,

I just want to ask you whether are you implementing the script volumetric calculation pos laju for os commerce? because it seems now everyone have been using volumetric to calculate their shipping cost.</description>
		<content:encoded><![CDATA[<p>Hi sean,</p>
<p>I just want to ask you whether are you implementing the script volumetric calculation pos laju for os commerce? because it seems now everyone have been using volumetric to calculate their shipping cost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pos Malaysia Shipping Widget for your website</title>
		<link>http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/comment-page-1/#comment-3173</link>
		<dc:creator>Pos Malaysia Shipping Widget for your website</dc:creator>
		<pubDate>Sun, 28 Feb 2010 09:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lolyco.com/sean/?p=787#comment-3173</guid>
		<description>[...] Tuesday I started &#8216;ripping&#8217; Pos Malaysia&#8217;s shipping rates. The whole problem is the difficulty of access to their rates, so having my own set would make the [...]</description>
		<content:encoded><![CDATA[<p>[...] Tuesday I started &#8216;ripping&#8217; Pos Malaysia&#8217;s shipping rates. The whole problem is the difficulty of access to their rates, so having my own set would make the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cross-domain javascript widget, no JSON, no AJAX</title>
		<link>http://blog.lolyco.com/sean/2010/02/25/pos-malaysia-shipping-quote-part-2/comment-page-1/#comment-3166</link>
		<dc:creator>Cross-domain javascript widget, no JSON, no AJAX</dc:creator>
		<pubDate>Sat, 27 Feb 2010 16:25:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lolyco.com/sean/?p=787#comment-3166</guid>
		<description>[...] I may be doing something terribly wrong. I hope the Internet will tell me. I wanted to make a widget so that I could showcase some AJAX-accessible shipping quotes I&#8217;d put on spider.my, but demonstrate accessibility from another site. I&#8217;d never written much javascript before this week, so I was very pleased that my first attempt worked so quickly &#8211; and then I discovered the Same Origin Policy (SOP). My first attempt was just some javascript that dynamically created the HTML (just thought &#8211; shouldn&#8217;t the widget markup match the document&#8217;s doctype?) elements of the widget, and then responded to user input by sending a request for a shipping quotation to the XML responder I wrote a few days ago. [...]</description>
		<content:encoded><![CDATA[<p>[...] I may be doing something terribly wrong. I hope the Internet will tell me. I wanted to make a widget so that I could showcase some AJAX-accessible shipping quotes I&#8217;d put on spider.my, but demonstrate accessibility from another site. I&#8217;d never written much javascript before this week, so I was very pleased that my first attempt worked so quickly &#8211; and then I discovered the Same Origin Policy (SOP). My first attempt was just some javascript that dynamically created the HTML (just thought &#8211; shouldn&#8217;t the widget markup match the document&#8217;s doctype?) elements of the widget, and then responded to user input by sending a request for a shipping quotation to the XML responder I wrote a few days ago. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

