<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Disqus - Latest Comments for chris_f</title><link>http://disqus.com/by/chris_f/</link><description></description><atom:link href="http://disqus.com/chris_f/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Tue, 04 Nov 2008 16:54:47 -0000</lastBuildDate><item><title>Re: The Problem With Local Connection - I hereby decree - Short thoughts by David LeMieux</title><link>http://www.iherebydecree.com/archive/id/836#comment-3494337</link><description>&lt;p&gt;I've run into this problem as well and did some digging into the root cause.  I don't work for Adobe and don't know 100% for sure how they're doing things, but I think I have a pretty good clue.  I've added comments to the bug based on what I found, but figured it would be useful for others if I commented here as well.  From my digging, it appears that the limit to 8 LocalConnections is due to the way OS X is configured and how LocalConnections work (or appear to work).  It looks like Adobe is using shared memory for the communication to take place.  By default, OS X only allows 8 shared memory segments per user.  You can change this setting and I have confirmed that increasing the number of shared memory segments per user results in more LocalConnections succeeding.  Adobe still definitely has a bug since they're not bubbling up any error when they exceed the number of allowed segments though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">chris_f</dc:creator><pubDate>Tue, 04 Nov 2008 16:54:47 -0000</pubDate></item></channel></rss>