<?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: Crossroads: LMB^Box FilePress</title>
	<atom:link href="http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/feed/" rel="self" type="application/rss+xml" />
	<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/</link>
	<description>Thinking Outside ...</description>
	<lastBuildDate>Thu, 29 Jul 2010 00:10:09 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Thomas</title>
		<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/comment-page-1/#comment-561</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Tue, 14 Jun 2005 17:33:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.lmbbox.com/?p=46#comment-561</guid>
		<description>I understand where you&#039;re coming from! I am going to put in both because it is just the best thing to do right now. One option (Filesystem Functions) has problems on shared hosting servers with the ownership of the file uploaded. The other option (FTP Functions) has problems with bandwidth usage; every file uploaded is added twice to your bandwidth (I believe ...). I&#039;m hoping just to finish up the last beta version in the next day. Thanks for your support!</description>
		<content:encoded><![CDATA[<p>I understand where you&#8217;re coming from! I am going to put in both because it is just the best thing to do right now. One option (Filesystem Functions) has problems on shared hosting servers with the ownership of the file uploaded. The other option (FTP Functions) has problems with bandwidth usage; every file uploaded is added twice to your bandwidth (I believe &#8230;). I&#8217;m hoping just to finish up the last beta version in the next day. Thanks for your support!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Danny</title>
		<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/comment-page-1/#comment-560</link>
		<dc:creator>Danny</dc:creator>
		<pubDate>Tue, 14 Jun 2005 15:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.lmbbox.com/?p=46#comment-560</guid>
		<description>It should look good when it&#039;s finished! I think you should put both in, purely because i don&#039;t &lt;em&gt;quite&lt;/em&gt; understand what you&#039;re saying. (Please don&#039;t try to explain)

 :P

Thanks, keep up the good work, it&#039;s much appreciated,
Danny</description>
		<content:encoded><![CDATA[<p>It should look good when it&#8217;s finished! I think you should put both in, purely because i don&#8217;t <em>quite</em> understand what you&#8217;re saying. (Please don&#8217;t try to explain)</p>
<p> :P</p>
<p>Thanks, keep up the good work, it&#8217;s much appreciated,<br />
Danny</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/comment-page-1/#comment-559</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Sat, 11 Jun 2005 23:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.lmbbox.com/?p=46#comment-559</guid>
		<description>Well, I&#039;ve come to the conclusion that the best thing for the plugin is to have both Filesystem and FTP Fucntions included and the user sets which to use. I looked at alot of info/reviews/comments on PHP&#039;s CGI API vs Apache Module API and I believe even though the CGI API has some more security and good features, the downsides of it far out weigh the ups. :wallbash_tb: With CGI API, every single HTTP call is forced to open a new process to PHP which adds great demand of the server. Also many of the builtin PHP variables like $_SERVER will have problems with their values/settings. :thumbdown_tb:

So the best thing to do is use PHP as an Apache Module, and I&#039;ll make the default settings use the FTP Functions to add the files using the plugin. Then there will also be the option to use the Filesystem Functions as well. The only real downside to using the FTP Functions to add/edit/manage/modify/remove files is that it adds to your bandwidth because your using FTP (I believe that it does ... :ponder_tb: ).

Oh by the way everyone, thanks for all your help ... :blink_tb:  :dunce_tb:  :dry_tb:  :down_tb:</description>
		<content:encoded><![CDATA[<p>Well, I&#8217;ve come to the conclusion that the best thing for the plugin is to have both Filesystem and FTP Fucntions included and the user sets which to use. I looked at alot of info/reviews/comments on PHP&#8217;s CGI API vs Apache Module API and I believe even though the CGI API has some more security and good features, the downsides of it far out weigh the ups. <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/wallbash.gif" alt=":wallbash_tb:" /> With CGI API, every single HTTP call is forced to open a new process to PHP which adds great demand of the server. Also many of the builtin PHP variables like $_SERVER will have problems with their values/settings. <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/thumbdown.gif" alt=":thumbdown_tb:" /></p>
<p>So the best thing to do is use PHP as an Apache Module, and I&#8217;ll make the default settings use the FTP Functions to add the files using the plugin. Then there will also be the option to use the Filesystem Functions as well. The only real downside to using the FTP Functions to add/edit/manage/modify/remove files is that it adds to your bandwidth because your using FTP (I believe that it does &#8230; <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/ponder.gif" alt=":ponder_tb:" /> ).</p>
<p>Oh by the way everyone, thanks for all your help &#8230; <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/blink.gif" alt=":blink_tb:" />  <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/dunce.gif" alt=":dunce_tb:" />  <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/dry.gif" alt=":dry_tb:" />  <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/down.gif" alt=":down_tb:" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/comment-page-1/#comment-558</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Sat, 11 Jun 2005 01:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.lmbbox.com/?p=46#comment-558</guid>
		<description>I&#039;ve been doing lots of researching online this evening and I&#039;ve found some other help/info. :ponder_tb: One option which would take care of all these problems is if your PHP is run via the CGI API instead of the Apache Module API. What does this mean? Well, PHP that is run via the CGI API has the PHPsuexec feature enabled which lets all process of PHP run under the user&#039;s account. Now when you upload/add/create/modify any file or folder, that file or folder will have your user as the owner and group on a Linux/Unix system, taking care of the problem. :thumbup_tb: I&#039;m not sure about the security issues with the CGI API, but from what I&#039;ve read the CGI API should be more secure than the Apache Module API! There is a small problem though ... YOU would have to add to the top of all your php files something like this &lt;code&gt;#!/usr/bin/php&lt;/code&gt; that states the path to the PHP executible file. :thumbdown_tb: But that&#039;s not really all that hard to do ...

I&#039;m doing some more indeepth research on these topics to dig up some dirt on both options. I think I&#039;ll just end up adding support for both standard filesystem and ftp uploads and management functions for LMB^Box FilePress and you&#039;ll set which on to use in the Options page. I would really like feedback from all of you out there ...  :huh_tb:</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been doing lots of researching online this evening and I&#8217;ve found some other help/info. <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/ponder.gif" alt=":ponder_tb:" /> One option which would take care of all these problems is if your PHP is run via the CGI API instead of the Apache Module API. What does this mean? Well, PHP that is run via the CGI API has the PHPsuexec feature enabled which lets all process of PHP run under the user&#8217;s account. Now when you upload/add/create/modify any file or folder, that file or folder will have your user as the owner and group on a Linux/Unix system, taking care of the problem. <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/thumbup.gif" alt=":thumbup_tb:" /> I&#8217;m not sure about the security issues with the CGI API, but from what I&#8217;ve read the CGI API should be more secure than the Apache Module API! There is a small problem though &#8230; YOU would have to add to the top of all your php files something like this <code>#!/usr/bin/php</code> that states the path to the PHP executible file. <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/thumbdown.gif" alt=":thumbdown_tb:" /> But that&#8217;s not really all that hard to do &#8230;</p>
<p>I&#8217;m doing some more indeepth research on these topics to dig up some dirt on both options. I think I&#8217;ll just end up adding support for both standard filesystem and ftp uploads and management functions for LMB^Box FilePress and you&#8217;ll set which on to use in the Options page. I would really like feedback from all of you out there &#8230;  <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/huh.gif" alt=":huh_tb:" /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wordpress Plugin Competition Blog</title>
		<link>http://lmbbox.com/2005/06/10/crossroads-lmbbox-filepress/comment-page-1/#comment-557</link>
		<dc:creator>Wordpress Plugin Competition Blog</dc:creator>
		<pubDate>Fri, 10 Jun 2005 19:03:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.lmbbox.com/?p=46#comment-557</guid>
		<description>&lt;strong&gt;Crossroads: LMB^Box FilePress&lt;/strong&gt;

I&#039;m at a crossroads point in my LMB^Box FilePress plugin for WordPress. I&#039;m calling out for everyone&#039;s input as to what they think/know will be better! :help_tb:

The Problem
Ok. Many of you may know about the problem with file management using ...</description>
		<content:encoded><![CDATA[<p><strong>Crossroads: LMB^Box FilePress</strong></p>
<p>I&#8217;m at a crossroads point in my LMB^Box FilePress plugin for WordPress. I&#8217;m calling out for everyone&#8217;s input as to what they think/know will be better! <img class="lmbbox_smileys_img" src="http://www.lmbbox.com/wp-content/plugins/lmbbox-smileys/smileys/tb/help.gif" alt=":help_tb:" /></p>
<p>The Problem<br />
Ok. Many of you may know about the problem with file management using &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
