/*
 * este es el shorthand para
 * $(document).ready(function() { ... });
 */
$(function(){   

    //función recursiva
    // target es el selector del formulario
    var ajaxForm = function(target){ 

        $(target).ajaxForm( {
            target: '#cboxLoadedContent',
            beforeSubmit:  function()
            {
                ... // Ejecutar codigo antes del ajax
            },
            success: function()
            {
                $.colorbox.resize();
                ajaxForm(target);
            }
        });
    }

    // Llamo la función recursiva desde colorbox
    $("a.classoflink").colorbox({
            onComplete:function()
            {
                $.colorbox.resize();
                ajaxForm('form.caption');
            }
    });
});

Bueno, espero que les sea de utilidad. Esto es todo por este post.
Nota: Se supone que tenemos cargadas las correspondientes librerias (jquery, jquery.form y colorbox ).

http://www.businessinsider.com/how-to-run-firefox-4-and-3-simultaneously-in-mac-os-x-with-multiple-firefox-profiles-2011-3

paso 1:
/etc/init.d/mysql stop

paso 2:
mkdir /var/lib/mysql1
mkdir /var/lib/mysql2

chown mysql.mysql /var/lib/mysql1
chown mysql.mysql /var/lib/mysql2

mkdir /var/run/mysqld1
mkdir /var/run/mysqld2

chown mysql.mysql /var/run/mysqld1
chown mysql.mysql /var/run/mysqld2

paso 3:

mysql_install_db –user=mysql –datadir=/var/lib/mysql1/
mysql_install_db –user=mysql –datadir=/var/lib/mysql2/

paso 4:

[mysqld_multi]
mysqld = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin

[mysqld1]
datadir = /var/lib/mysql1
socket = /var/lib/mysql1/mysql.sock
pid-file = /var/run/mysqld1/mysqld1.pid
user = mysql
port = 3306
server-id=1
log-bin=mysql-bin
log-error=/var/log/mysqld1.log

[mysqld2]
datadir=/var/lib/mysql2
socket=/var/lib/mysql2/mysql.sock
pid-file = /var/run/mysqld2/mysqld2.pid
user=mysql
port = 3307
server-id=2

Correr !!!

/etc/init.d/mysqld_multi start

I’ve recently came across NGINX (http://wiki.nginx.org) which seems to be a very well respected replacement of our dear friend APACHE.

I’ve been told that is faster, stable and it’s driven by newer technology. We’ll start testing int in house these days (specially the streaming capabilites).

Cheers,

-Fabian

If you ever face a poor performance symfony app on a LAMP server, you’ll might want to check on the following aspects:

To start with, always check your application (codebase) to find out bad programming practices such as:

• Doctrine (amount of queries executed)
• HTML/CSS content (yslow firefox add on is very useful)

Then continue with the OS level application such as apache. There is mod call server status that will take a snapshot of apache utilization at a certain time, this will provide information such as:

• threads open
• resources allocated to each thread.

Last but not least, look at the hardware utilization. We’ve succesfully used MUNIN to monitor the LAMP performance. It provides a historical view of the server metrics that will point out any performance bottleneck.

Lets say, I’m on a on a page that let me input some data, and uses that information to create metatags over the page.

The input is not validated at all ,not in the input and not when writing the metatag component.(more common than you may think…)
Now, you could write data like this

tag”/><script/type=’text/javascript’>alert(‘message’);</script><meta name=”fake” content=”fake

Then, each person that visits this page will get an alert pop up.
Of course you can execute any code, and not just a naive alert.

What is happening?
Well , the application is just adding the data between quotes of
<meta name=”tags” content=”______________” />
so if you input:
selenium
The rendered tag would look like,
<meta name=”tags” content=”selenium” />

So far, so good.
But when we add data like:
tag”/><script/type=’text/javascript’>alert(‘message’);</script><meta name=”fake” content=”fake
The rendered tag would look like,
<meta name=”tags” content=”tag”/><script/type=’text/javascript’>alert(‘message’);</script><meta name=”fake” content=”fake” />

And this is a correct html, but, with our script.

So,how can we prevent this?
Again, this is just for starters.
Validation:
Use back-end validation and front-end validation.
Back end validation is the real deal here.In my opinion,you should think of front-end validation
just as a way to make the validations more user friendly, but not as a security measure.

Escaping:
In cases like the example above, a solution could be to escape all string before writing them to a page.
But of course, you have to do this in every place you are writing this string down.
Remember that if you do not use validations, the malicious string is already in.

In java, you have easy ways to escape strings, like:StringEscapeUtils.escapeHtml(String)

Mostly important, it pretty much cover some basic x-browser issues, provides a way to do easy self-clearing floats, supports HTML5.

Here it is, give it a look and share your comments.

http://html5reset.org/#about

You probably encounter a similar problem as well.For instance, think about a paginator.You need ,maybe,10/25/100 results (not all of them) to show.But, at the same time, you need the total amount of items, to know how many pages will be.If you are using mysql,  SQL_CALC_FOUND_ROWS can be a good choice.

So,what is SQL_CALC_FOUND_ROWS?

A SELECT statement may include a LIMIT clause to restrict the number of rows the server returns to the client.

In some cases, it is desirable to know how many rows the statement would have returned without the LIMIT, but without running the statement again.
To obtain this row count, include a SQL_CALC_FOUND_ROWS option in the SELECT statement, and then invoke FOUND_ROWS() afterward:

mysql> SELECT SQL_CALC_FOUND_ROWS * FROM tbl_name
-> WHERE id > 100 LIMIT 10;
mysql> SELECT FOUND_ROWS();

The second SELECT returns a number indicating how many rows the first SELECT would have returned if it had been written without the LIMIT clause.

Looks handy, right ?

Es todo automatico, traduce utilizando el motor de google o bing, y ademas se puede editar al vuela la traduccion con tanto de historial! Increible herramienta!