<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Vallery.net &#187; php</title>
	<atom:link href="http://vallery.net/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>http://vallery.net</link>
	<description>personal homepage of Jason Vallery</description>
	<lastBuildDate>Thu, 08 Apr 2010 22:45:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Extracting emails from Gmail and Google Apps for Domains</title>
		<link>http://vallery.net/2008/01/20/extracting-emails-from-gmail-and-google-apps-for-domains/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=extracting-emails-from-gmail-and-google-apps-for-domains</link>
		<comments>http://vallery.net/2008/01/20/extracting-emails-from-gmail-and-google-apps-for-domains/#comments</comments>
		<pubDate>Sat, 19 Jan 2008 22:09:52 +0000</pubDate>
		<dc:creator>jvallery</dc:creator>
				<category><![CDATA[Random Thoughts]]></category>
		<category><![CDATA[ec2]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[projects]]></category>

		<guid isPermaLink="false">http://vallery.net/2008/01/20/extracting-emails-from-gmail-and-google-apps-for-domains/</guid>
		<description><![CDATA[First off, I&#8217;ll get the link out of the way. If you go to http://vallery.net/gmail/ you can see this application in action. Now a little bit more about it. I discovered that over the years I haven&#8217;t exactly been great about maintaining my addressbook. I&#8217;ve lost touch of many of acquaintances that I have had [...]]]></description>
			<content:encoded><![CDATA[<p>First off, I&#8217;ll get the link out of the way.  If you go to <a href="http://vallery.net/gmail/">http://vallery.net/gmail/</a>  you can see this application in action.  Now a little bit more about it.</p>
<p>I discovered that over the years I haven&#8217;t exactly been great about maintaining my addressbook. I&#8217;ve lost touch of many of acquaintances that I have had casual communication with. I realized that their email addresses where trapped in the deep bowels of my Gmail account, if only there was some way to extract them. I quickly realized that using the newly released IMAP protocol I could probe every message and then extract out the email addresses from it, and in some cases even additional data like the first and last name. I started playing around with the scripting a bit and came up with what I have now. This tool goes out to the Gmail IMAP server and downloads the message header from ever email that is stored in my Gmail account (except the SPAM folder). It pulls them into a master list, along with the first and last name if available. After all of the emails have been extracted it calculates some basic statistics including frequency of occurrence, which it users to sort them on. All of this information is then exported into CSV files that are compatible with many different applications.</p>
<p>While doing this I discovered an additional use for this data. On many of the social networking sites like Facebook and LinkedIn they will allow you to import a contact list file and find everyone that has registered for the service that you already know. This turned out to be a really killer app for this functionality. The only challenge was that they limit your ability to upload contacts to about 2,000 at one go. I added some additional functionality to my extract that &#8220;chunked&#8221; the file into several files, each with 2,000 email addresses in it. This allowed me to upload my newly discovered contacts a bit at a time, which worked very well.</p>
<p>If you would like to extract the email addresses from your Gmail or Google Apps for Domains account head over to <a href="http://vallery.net/gmail/">http://vallery.net/gmail/</a> and give it a whirl!</p>
]]></content:encoded>
			<wfw:commentRss>http://vallery.net/2008/01/20/extracting-emails-from-gmail-and-google-apps-for-domains/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Debug your outbound POST and GET requests</title>
		<link>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=debug-your-outbound-post-and-get-requests</link>
		<comments>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/#comments</comments>
		<pubDate>Thu, 17 May 2007 19:27:13 +0000</pubDate>
		<dc:creator>jvallery</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[get]]></category>
		<category><![CDATA[lamp]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[post]]></category>
		<category><![CDATA[projects]]></category>

		<guid isPermaLink="false">http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/</guid>
		<description><![CDATA[I work a lot with different types of web services. I find when I&#8217;m building an application that has to post data off to a remote service that it can be difficult to debug where the problems are. I can&#8217;t always see an exact copy of the HTTP request that I am sending, and therefore [...]]]></description>
			<content:encoded><![CDATA[<p>I work a lot with different types of web services.  I find when I&#8217;m building an application that has to post data off to a remote service that it can be difficult to debug where the problems are.  I can&#8217;t always see an exact copy of the HTTP request that I am sending, and therefore how the remote service sees my call.  I created a simple little app that when called will return exactly what it was sent.  You can pass in variables in a POST or GET, and it will just spit them right back at you along with whatever HTTP headers were sent by your client.</p>
<p><!---more--></p>
<p>If you point your browser over to <a href="http://vallery.net/postback/index.php">http://vallery.net/postback/index.php</a> you can see it in action.  It will report back to you exactly how your browser is identifying itself, including any cookies you might have received from my word press blog!</p>
<p>Now the next time you are writing an application and you want to debug your outbound posts, just send them over to the above URL and it will respond with exactly what it received.</p>
<p>Pretty cool!</p>
]]></content:encoded>
			<wfw:commentRss>http://vallery.net/2007/05/17/debug-your-outbound-post-and-get-requests/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
