<?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>Communication Archives &#8211; My Virtual Vision</title>
	<atom:link href="https://blog.myvirtualvision.com/tag/communication/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.myvirtualvision.com/tag/communication/</link>
	<description>My thoughts on application delivery</description>
	<lastBuildDate>Wed, 19 Jun 2013 12:27:40 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>
<site xmlns="com-wordpress:feed-additions:1">19765378</site>	<item>
		<title>Citrix: XenDesktop 5 Logon Process and Communication Flow</title>
		<link>https://blog.myvirtualvision.com/2011/04/14/citrix-xendesktop-5-logon-process-and-communication-flow/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=citrix-xendesktop-5-logon-process-and-communication-flow</link>
					<comments>https://blog.myvirtualvision.com/2011/04/14/citrix-xendesktop-5-logon-process-and-communication-flow/#comments</comments>
		
		<dc:creator><![CDATA[Kees Baggerman]]></dc:creator>
		<pubDate>Thu, 14 Apr 2011 10:07:41 +0000</pubDate>
				<category><![CDATA[Citrix]]></category>
		<category><![CDATA[XenDesktop]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Logon]]></category>
		<category><![CDATA[Process]]></category>
		<guid isPermaLink="false">http://blog.myvirtualvision.com/?p=461</guid>

					<description><![CDATA[Martijn Bosschaart just posted CTX128909 on twitter, this article contains the following information on XenDesktop 5 Logon Process and Communication Flow: &#160; The user device submits credentials to the Web Interface site. Web Interface passes the user credentials to the controller. Controller verifies user authorization by performing a Microsoft Active Directory query with the end [&#8230;]]]></description>
		
					<wfw:commentRss>https://blog.myvirtualvision.com/2011/04/14/citrix-xendesktop-5-logon-process-and-communication-flow/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">461</post-id>	</item>
		<item>
		<title>Citrix: Communication Ports Used By Citrix Technologies</title>
		<link>https://blog.myvirtualvision.com/2011/04/14/citrix-communication-ports-used-by-citrix-technologies/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=citrix-communication-ports-used-by-citrix-technologies</link>
					<comments>https://blog.myvirtualvision.com/2011/04/14/citrix-communication-ports-used-by-citrix-technologies/#respond</comments>
		
		<dc:creator><![CDATA[Kees Baggerman]]></dc:creator>
		<pubDate>Thu, 14 Apr 2011 10:02:11 +0000</pubDate>
				<category><![CDATA[Citrix]]></category>
		<category><![CDATA[XenApp]]></category>
		<category><![CDATA[XenDesktop]]></category>
		<category><![CDATA[Communication]]></category>
		<category><![CDATA[Overview]]></category>
		<category><![CDATA[Ports]]></category>
		<guid isPermaLink="false">http://blog.myvirtualvision.com/?p=457</guid>

					<description><![CDATA[Citrix just posted an updated version of the PDF that describes the communication ports used by Citrix technologies. It&#8217;s a good reference document when talking about communications and for example which ports to open on a firewall in order to get proper communication between different technologies. The introduction from the PDF: This document provides an [&#8230;]]]></description>
		
					<wfw:commentRss>https://blog.myvirtualvision.com/2011/04/14/citrix-communication-ports-used-by-citrix-technologies/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">457</post-id>	</item>
	</channel>
</rss>
