[fw-general] Wiki is dead

2007-12-06 Thread Elisamuel Resto
Lovely greeting when I go to see data in the wiki:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /wiki/display/ZFDEV/Home.

Reason: Error reading from remote server


Re: [fw-general] ZF is ubeatable BUT...

2007-07-21 Thread Elisamuel Resto
On Sat, 21 Jul 2007 07:35:42 -0700 (PDT), Pádraic Brady
[EMAIL PROTECTED] wrote:
 It's this term gets me every time: greatly reduce the code overhead.
 
 There is no such overhead which has any impact on performance. Once the
 files are present on the server, their overall total size is irrelevant.
 The only size that then matters at that point is what is read from disk,
 and loaded into RAM - which is certainly not the whole framework ;).
 
 I think a lot of people are bound to make comparisons to PEAR as a code
 repository. The purpose of the framework isn't simply to implement MVC,
 it's to implement MVC packaged with high value commonly required
components
 which you may optionally utilise. Maybe not everyone will need an
optional
 component like Zend_Feed, but a lot of other people will. Enough that
 leaving it out would be inconvenient for many users. There's quite a lot
of
 value attached to optional, loosely coupled components for many
developers.
  
 Pádraic Brady
 http://blog.astrumfutura.com
 http://www.patternsforphp.com
 
 
 - Original Message 
 From: till [EMAIL PROTECTED]
 To: Zuhair [EMAIL PROTECTED]
 Cc: fw-general@lists.zend.com
 Sent: Saturday, July 21, 2007 10:42:40 AM
 Subject: Re: [fw-general] ZF is ubeatable BUT...
 
/snip

I agree, but the thing is that most people assume that the size of whatever
you download will be the size of whatever will be loaded into the memory
for running the app, unless they know how the software works. In the other
posts, however, it is referenced about the filesize and amount, and how the
average user will only use a subset of all the components.

I for one, use the MVC+Smarty, Zend_Mail, Zend_Feed and a few classes of my
own. The trick here is to have a central install of the Framework and
update include_path accordingly. This not only decreases the efforts
required to upgrade, but you can use whatever you need from whatever site
without much hassle. At least, for me, this is the best approach of all I
could think of, since I run the code off of SVN and is updated about once a
week, depending if something broke with an update or not (so far was the
introduction of the automatic renderer helper... which I disabled since I
don't use it, but I do plug the Smarty class in) too long ago was quickly
solved from my behalf.

PS: Pádraic, are you aware that patternsforphp.com is expired? Just a
heads-up.

-- 
Elisamuel Resto [EMAIL PROTECTED]
www.dragonboricua.net / www.sourcemage.org
Source Mage GNU/Linux / GPG ID: 0x18615F19
B66D 1C2A E8EE B922 1D9C D98F D2D5 FB61 1861 5F19



[fw-general] Zend Framework on DreamHost

2007-01-10 Thread Elisamuel Resto

Hello,

  Anybody has actually gotten the Framework working on a DreamHost account?
I'm hitting the ground hard with mod_rewrite looping with every ruleset I've
tried, even ones I had that had worked before, and ones that were on the
manuals and tutorials.


Regards,
E. Resto