The idea is that all of these sites should have the same "look and feel" but there will probably be several differences between the web applications. Virtually all of these web applications will take some input files, do some processing on them, and give output files. Some of the web applications are very large. Some will share files with others, and some will keep their own files to themselves. We want a single sign-in for everything on the portal.

I'm wanting to know from more experienced people what is the best way to design something like this? Should I do this on one Zend Framework project, or should each webapp be a separate project? If separate is there a good way to avoid redundancy in things such as layout and stylesheets? If combined is there a good way to manage SVN version control for each separate project? I recognize some of this may come from my limited knowledge of both Zend Framework and the MVC pattern (though I've been reading up on it for a while now and have a decent understanding, just little experience).

I'd greatly appreciate any and all advice/suggestions on this, especially from anyone with experience in projects similar to this.

Thanks,
-Steve

what would be the best way to isollate persistence code from model? So, that I could just create new class and use it instead of currently used.

If I create an interface for repository and then create different implementations, and use abstract factory to create instances of those implementations?

Or am I totally lost with these thoughts?

-- Miika

http://giorgiosironi.blogspot.com/2009/ … bject.html

@daniel - I am still learning in both directions. I understand the technical difference (from a high level) between the two, but deciding with one to use on a project basis is something I am still working on. Let us know what you decide.

$bootstrap = Zend_Controller_Front::getInstance()->getParam('bootstrap');
        $config = $bootstrap->getOption('smtp');
        $smtpHost   = new Zend_Mail_Transport_Smtp($config['server'], $config['config']);

        //Create Zend_Mail object.
        $MailObj = new Zend_Mail();

        //Initialize parameters.
        $MailObj->setBodyHTML($emailMessage);
        $MailObj->setFrom($config['fromEmail'], $config['fromName']);
        $MailObj->addTo($to);
        $MailObj->setSubject($subject);
        $MailObj->setReplyTo('donotreply@test.com', 'Test test test');
       
        $from_name="Test";
        $from_address="donotreply@test.com";

I took this plug-in from the Internet and amended it a bit.

You need to add the following plgin to your application/plugins folder:

inside the file application/plugins/Ssl.php :

class Application_Plugin_Ssl extends Zend_Controller_Plugin_Abstract {

    /**
     * Check the application.ini file for security settings.
     * If the url requires being secured, rebuild a secure url
     * and redirect.
     *
     * @param Zend_Controller_Request_Abstract $request
     * @return void
     */
    public function preDispatch(Zend_Controller_Request_Abstract $request) {

        $shouldSecureUrl = false;

        $options = Zend_Registry::getInstance()->get('config');

        if (!empty($options->ssloptions->modules->{$request->module}->{$request->controller}->require_ssl) ||
                !empty($options->ssloptions->modules->{$request->module}->{$request->controller}->{$request->action}->require_ssl)) {
                $shouldSecureUrl = true;
        }

        if ($shouldSecureUrl) {
            $this->_secureUrl($request);
        } else {
            $this->_unsecureUrl($request);
        }
    }

    protected function _secureUrl(Zend_Controller_Request_Abstract $request) {

        $server = $request->getServer();
        $hostname = $server['HTTP_HOST'];
        $uri = $server['REQUEST_URI'];

        if (!$request->isSecure()) {
            //url scheme is not secure so we rebuild url with secureScheme
            $url = Zend_Controller_Request_Http::SCHEME_HTTPS . "://" . $hostname . $uri;
            $redirector = Zend_Controller_Action_HelperBroker::getStaticHelper('redirector');
            $redirector->setGoToUrl($url);
            $redirector->redirectAndExit();
        }
    }

    protected function _unsecureUrl(Zend_Controller_Request_Abstract $request) {

        $server = $request->getServer();
        $hostname = $server['HTTP_HOST'];
        $uri = $server['REQUEST_URI'];

        if ($request->isSecure()) {
   
            $url = Zend_Controller_Request_Http::SCHEME_HTTP . "://" . $hostname . $uri;
           
            $redirector = Zend_Controller_Action_HelperBroker::getStaticHelper('redirector');
            $redirector->setGoToUrl($url);
            $redirector->redirectAndExit();
        }
    }

}

At your config.ini file you could specify the action or controller you want to be secured, something like this:

    <ssloptions>
        <modules>
            <default>
                <booking>
                    <require_ssl>true</require_ssl>
                </booking>
                <account>
                    <require_ssl>true</require_ssl>
                </account>
            </default>
        </modules>
    </ssloptions>

This will make the controller booking inside the default module to be directed to a secure page.

Of course you have to enable the plugin in your boostrap file like this.

    protected function _initPlugins()
    {

        $this->bootstrap("frontcontroller");
        $fc = $this->getResource("frontcontroller");

   
               $fc->->registerPlugin(new Application_Plugin_Ssl);
           

        return $fc;
    }

Thanks Mazen

Using login would be a great help for an unwanted using of accounts.
Putting login before it start is somehow prevents our account in unwanted using our accounts or destroying it.

We can prevent spammers or bots if login is present.
I would recommend that login should have a three attempts and when he/she meets the 3rd attempts the application will close.

thanks