- ThinkPHP Network |
- ThinkPHP
- Enterprise LAMP Support
- Mayflower
- PHP Training
- PHProjekt
- PHP-Center
- ThinkForge.org
Quicksearch
Syndicate This Blog
Secure your site
SektionEins is the Web Security Company. It was founded by Mayflower GmbH and Stefan Esser and provides Security Audits, Consulting and Security Trainings. Please contact us if you need securing your web application.Categories
Blogroll
We read:
Planet PHP
Planet MySQL
Exciting E-Commerce
E-Commerce Blog
Fischmarkt
fukami
Lars Jankowfsky
Themenblog
Thomas Bachem
Matt Asay on OpenSource
Joel on Software
Ibrahim Evsan
Hasematzel
Techcrunch
Indiskretion Ehrensache
Sichelputzer
Alexander Schwinn
Managing Tech
F-LOG-GE
trycatchfinally
PHProjekt Developer Blog
phpMyFAQ devBlog
phpMyFAQ 2.6.7 Released!
Thursday, July 29. 2010
Status update for phpMyFAQ 2.6.7
Sunday, July 25. 2010
Status update for phpMyFAQ 2.6.7
Tuesday, July 6. 2010
Technorati
ThinkPHP /dev/blog
Open Source
Wednesday, March 10. 2010
PHProjekt V6 kicks out of the door on March 18th
PHProjekt V6, our little beastbee and Open Source project management software, kicks out of the door on March 18th as GA. It's a complete rewrite (and thus, a major version update was needed) with Zend Framework and dojo and now licensed under LGPL (earlier versions were licensed under GPL). You may ask what you want to do until March 18th? Well, besides eating popcorn for Film@11:
- follow the little bee @phprojekt6
- get social with PHProjekt at its Facebook fanpage
- visit the PHProjekt blog for regular updates
- check out the code at github
- want to talk to the developers or contribute? /join #phprojekt on freenode (irc.freenode.org)
- ... and, finally, try out the demo at p6.phprojekt.com
The bee is watching you!
Thursday, March 4. 2010
A comet over PHProjekt 6
So far PHProjekt 6 (P6, see http://phprojekt.com) is already enhanced with nice AJAX workflows and snappy user-experience. Nevertheless, we discussed a way to provide synchronous communication and direct information within the application.
Everybody knows GoogleMail with its easy to use frontend. Maybe you use it for your daily work. In GoogleMail, there is no need to refresh the page to receive a new mail, Google informs you automatically whenever a new mail is available. But how is this possible? The answer to this question is really simple: The server triggers a signal informing that a new mail is available. This technology is called Comet and describes a way how the server communicates with the client [see http://en.wikipedia.org/wiki/Comet_(programming) ].
Is there a way to use Comet for P6? As P6 works with a lot of users, it is important for me as a user to be informed when somebody has changed something in my projects or has added an urgent todo. The list where a notification could be triggered is long, but at the moment, only email notifications are sent immediately. So, what we need in P6 are real-time notifications. With real-time notifications, for example, every time somebody changes something in my project, I receive a message in form of a highlighted info box. This looks like a typical use case for using Comet. And yes, Comet would be great for realizing this kind of real-time notification! But since the users love the handy system requirements (Apache Server and MySQL) and the ease of installation, something different is needed than a real Comet architecture, because all the Comet magic is based on a so called application server, e.g. Jetty, Persevere. Therefore, I decide to implement another (Comet-) technology, called Long Polling. You can find the name AJAX Polling for this technology, too.
The technology behind Long Polling is to open a connection from the client to the server and not to close this connection immediately. Ok, that´s fine, but how to open a connection and "hold" it? Opening a connection to the server is easy, a simple AJAX will do the trick. P6 uses the Dojo Toolkit for all its AJAX, so in this case I used the Dojo.xhrPost.
Since the HTTP protocoll is connection-based, at the server-side, a process is also needed that holds the connection and does not return . So, what I do to hold this connection open is to set a simple timeout during the execution of the server-side script, in my case I use sleep(). This is the basic idea of long polling, but the gimmick of this approach is to return earlier if something happens on the server-side. In other words, I open a connection to the server and check whether there are any changes, if not, the connection stays open for the maximum polling time. If yes, the response will be returned to the client immediately.
This diagram shows the basic workflow, and the lines below show the possible solution in PHP:
For P6 this means that I always save the following: the person who triggers an event, the event itself (e.g. somebody adds a new note), the item, the project, the creation time, the time until this message is valid, and the persons who should receive a frontend message from the database. The long polling loop checks whether there is anything new. If yes, it returns the data. If not, the polling loop starts again. Every event is saved in the database for a maximum of two minutes, except events in the future. Itis real-time – so itis possible to miss a message ;-)
One word about the Dojo Toolkit. The AJAX API of Dojo provides several functions to communicate with the server. The easiest way is to use dojo.xhrGet or dojo.xhrPost. I decided to use the Post version. Although the function has a property setTimeout, which allows you to set the time to wait for a response from the server, this is not needed, because of the sleep loops at the server side.
Now, let’s look at the downsides of the long polling approach. Yes, I partly agree with everybody who says that the permanent polling to the server causes massive traffic and server load, especially with an increasing number of users. But in the special case of P6 this is OK, because the number of users is manageable and in most cases, P6 runs in a local network. In addition, the frontend messages are configurable, You can set the polling loop and the number of requests to the database.
Considering all the facts and keeping in mind that P6 is designed to be a lightweight open source groupware, I am positive to say that the Long Polling technology is the right choice for P6.
Everybody knows GoogleMail with its easy to use frontend. Maybe you use it for your daily work. In GoogleMail, there is no need to refresh the page to receive a new mail, Google informs you automatically whenever a new mail is available. But how is this possible? The answer to this question is really simple: The server triggers a signal informing that a new mail is available. This technology is called Comet and describes a way how the server communicates with the client [see http://en.wikipedia.org/wiki/Comet_(programming) ].
Is there a way to use Comet for P6? As P6 works with a lot of users, it is important for me as a user to be informed when somebody has changed something in my projects or has added an urgent todo. The list where a notification could be triggered is long, but at the moment, only email notifications are sent immediately. So, what we need in P6 are real-time notifications. With real-time notifications, for example, every time somebody changes something in my project, I receive a message in form of a highlighted info box. This looks like a typical use case for using Comet. And yes, Comet would be great for realizing this kind of real-time notification! But since the users love the handy system requirements (Apache Server and MySQL) and the ease of installation, something different is needed than a real Comet architecture, because all the Comet magic is based on a so called application server, e.g. Jetty, Persevere. Therefore, I decide to implement another (Comet-) technology, called Long Polling. You can find the name AJAX Polling for this technology, too.
The technology behind Long Polling is to open a connection from the client to the server and not to close this connection immediately. Ok, that´s fine, but how to open a connection and "hold" it? Opening a connection to the server is easy, a simple AJAX will do the trick. P6 uses the Dojo Toolkit for all its AJAX, so in this case I used the Dojo.xhrPost.
dojo.xhrPost({
url: myUrl,
error: function(error, handle) {
handleError(myUrl, error);
},
load: function(response) {
if (false != response.data) {
showToaster(response.data);
}
},
handleAs: 'json'
});
Since the HTTP protocoll is connection-based, at the server-side, a process is also needed that holds the connection and does not return . So, what I do to hold this connection open is to set a simple timeout during the execution of the server-side script, in my case I use sleep(). This is the basic idea of long polling, but the gimmick of this approach is to return earlier if something happens on the server-side. In other words, I open a connection to the server and check whether there are any changes, if not, the connection stays open for the maximum polling time. If yes, the response will be returned to the client immediately.
This diagram shows the basic workflow, and the lines below show the possible solution in PHP:
$counter = 0;
$maxLoops = 4;
$data = array();
while ($counter != $maxLoops) {
$counter++;
$data = $this->getMessage($userId); // get data from database
if (false === empty($data)) {
return $data; // there is something new, return immediately
}
sleep(5); // nothing is new, sleep for 5 sec.
}
return $data; // return the empty array
For P6 this means that I always save the following: the person who triggers an event, the event itself (e.g. somebody adds a new note), the item, the project, the creation time, the time until this message is valid, and the persons who should receive a frontend message from the database. The long polling loop checks whether there is anything new. If yes, it returns the data. If not, the polling loop starts again. Every event is saved in the database for a maximum of two minutes, except events in the future. Itis real-time – so itis possible to miss a message ;-)
One word about the Dojo Toolkit. The AJAX API of Dojo provides several functions to communicate with the server. The easiest way is to use dojo.xhrGet or dojo.xhrPost. I decided to use the Post version. Although the function has a property setTimeout, which allows you to set the time to wait for a response from the server, this is not needed, because of the sleep loops at the server side.
Now, let’s look at the downsides of the long polling approach. Yes, I partly agree with everybody who says that the permanent polling to the server causes massive traffic and server load, especially with an increasing number of users. But in the special case of P6 this is OK, because the number of users is manageable and in most cases, P6 runs in a local network. In addition, the frontend messages are configurable, You can set the polling loop and the number of requests to the database.
Considering all the facts and keeping in mind that P6 is designed to be a lightweight open source groupware, I am positive to say that the Long Polling technology is the right choice for P6.
Saturday, November 28. 2009
Everybody can fork MySQL. But what about market penetration?
Oracle/MySQL - Project Peter - Monty's dreams for BSD license
Wednesday, November 25. 2009
PHP_CodeBrowser Release version 0.1.0
Mayflower is proud to announce the release of the open source tool PHP_CodeBrowser in the current version 0.1.0-alpha.
What is PHP_CodeBrowser
PHP_CodeBrowser is a tool mainly intended to be used in conjunction with CruiseControl. It provides a code browser for PHP files with syntax highlighting and colored error-sections found by quality assurance tools like PHPUnit or PHP_CodeSniffer. The visualisation of errors, warnings or notices, found by above mentioned kind of tools, is the real power of PHP_CodeBrowser. You may also use PHP_CodeBrowser as a stand alone version, but therefore you would need previous generated XML error files.
PHP_CodeBrowser features
PHP_CodeBrowser comes along with syntax highlighting, colored error sections and a smart clickable error overview. Supported are XML report files generated from following supported quality assurance tools:
Why should you use it
Because it's cool, and it helps strongly getting an complete overview over your code quality in single files.
Installation
If you would like to try out, please check out source directly from SVN:
svn co svn://phpunit.de/phpunit/phpcb/trunk PHP_CodeBrowser
or use pear installation routine:
pear config-set preferred_state alpha
pear channel-discover pear.phpunit.de
pear install --alldeps phpunit/PHP_CodeBrowser
For the integration in cruisecontrol, please have a look at the README file, or use the current version of phpUnderControl.
What is PHP_CodeBrowser
PHP_CodeBrowser is a tool mainly intended to be used in conjunction with CruiseControl. It provides a code browser for PHP files with syntax highlighting and colored error-sections found by quality assurance tools like PHPUnit or PHP_CodeSniffer. The visualisation of errors, warnings or notices, found by above mentioned kind of tools, is the real power of PHP_CodeBrowser. You may also use PHP_CodeBrowser as a stand alone version, but therefore you would need previous generated XML error files.
Integration in phpUnderControl
PHP_CodeBrowser features
PHP_CodeBrowser comes along with syntax highlighting, colored error sections and a smart clickable error overview. Supported are XML report files generated from following supported quality assurance tools:
- PHPUnit
- CPD
- Padawan
- CodeSniffer
Colored error sections
Why should you use it
Because it's cool, and it helps strongly getting an complete overview over your code quality in single files.
Clickable error list overview
Installation
If you would like to try out, please check out source directly from SVN:
svn co svn://phpunit.de/phpunit/phpcb/trunk PHP_CodeBrowser
or use pear installation routine:
pear config-set preferred_state alpha
pear channel-discover pear.phpunit.de
pear install --alldeps phpunit/PHP_CodeBrowser
For the integration in cruisecontrol, please have a look at the README file, or use the current version of phpUnderControl.