PAMP 1.0.2 Available

[jhnwkmn]

Version 1.0.2 of the Personal AMP - Apache, MySQL and PHP - stack for the S60 smartphone is now available. All components are released separately as well and can thus be installed individually.

Download: http://sourceforge.net/projects/pamp
Documentation: http://wiki.opensource.nokia.com/projects/PAMP

PAMP can be installed as standalone or on top of MWS (1.5).

Source:

svn co http://pamp.svn.sourceforge.net/svnroot/pamp/tags/pamp-1.0.2

CHANGES
httpd

• Default stack-size of threads increased to 0x10000 (was 0x5000).
• APR allows the IAP of a socket to be defined.
• mod_proxy and mod_proxy_http works.
• The command-line of httpd can be specified.
• API for storing the memory (heapmap, heapmin, stack) settings at the server.
• Loading of mod_python no longer forces httpd into single-thread mode.
• Blocking IO (default on Symbian currently) can now be turned off using the Symbian specific directive AlwaysUseBlockingIO, thus making it possible to experiment having KeepAlive On.
• A number of locking primitives enabled in APR.
• HTTPD_ROOT now always "c:/data/apache", but can be specified at runtime.
• Thread death detected in Symbian server.

mod_php

• xsl extension now included.
• dom extension now included.

MySQL

• Now based on MySQL 5.0.67

NOTE: PAMP still has quite a few rough edges. Do not try it out if you expect a polished product.

Have fun, and please report of problems you encounter.

Johan

[didacgil9]

I would like to know which are the limitations exiting with the MySQL running in PAMP.

For example, I have seen that if I make a table to grow more than 800 lines (it was around 64KB), the table is not readable anymore.

I want to avoid starting MySQL with the option --skip-grant-tables, so I have defined some users to have admin and view privileges each of them.

Well... those users can make queries from the MySQL GUI client in from Windows. But the PHP running in the Nokia, can not read anything at all.
GRANT SELECT ON test.* TO 'user'@'%'

As you see, the privileges are simple.

Even more, the admin user, when trying to create a table (it works with the option --skip-grant-tables), crashes Apache!!

Is there any special configuration in the php module that Apache is using to have MySQL connectivity?

Thank you

[jhnwkmn]

I would like to know which are the limitations exiting with the MySQL running in PAMP.

Unfortunately there is no exhaustive list of known limitations. PAMP was developed with limited resources and primarily as an experiment, so we had to cut quite a few corners.

For example, I have seen that if I make a table to grow more than 800 lines (it was around 64KB), the table is not readable anymore.

Thanks, that's valuable information.

...
Even more, the admin user, when trying to create a table (it works with the option --skip-grant-tables), crashes Apache!!

What's the setup in this case? You create the table via PHP running under Apache?

Is there any special configuration in the php module that Apache is using to have MySQL connectivity?

Do you refer to something else but the mysqli.default_user and friends in data/php/php.ini?

Br,
Johan

[didacgil9]

Unfortunately there is no exhaustive list of known limitations. PAMP was developed with limited resources and primarily as an experiment, so we had to cut quite a few corners.

Anyway, it's a great job. I would be able to reach those development skills in some years

What's the setup in this case? You create the table via PHP running under Apache?

Yes, right. it's just a simple PHP script that, when running with login "" and password "" and --skip-grant-tables, works fine but, when using "admin" "passwadmin" and NO --skip-grant-tables, does not work in PHP.
Of course, the user was created in MySQL, with grant privileges.

BTW, the following code crashes Apache because of mysql_error() method.

$connect = mysql_connect($user, $password, $db);
if (!$connect) echo "Error: ".mysql_error();

Do you refer to something else but the mysqli.default_user and friends in data/php/php.ini?

Well... I understand that just for the default user to make login in the database. I can always specify a user in the mysql_connection(), right? I least I should be able, no?