Re: [PHP] Acentos en tpl

[Richard Quadling]

2011/3/18 Lorena Monroy O. lorenamon...@yahoo.com:
 Hi everyone
 First, I'm so sorry to write in spanish , but when I suscribed I didn´t know 
 that was an english list. If I will needs again or to help I will write in 
 english like that. My english is not fluent, sorry again.

Your english is fine. My spanish is not.

-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Acentos en tpl

[Daniel Brown]

2011/3/17 Lorena Monroy O. lorenamon...@yahoo.com:
 Hola a todos
 Tengo un formulario que tiene dos paneles (.tpl), el cual maneja variables 
 que vienen de php con la funcion setVariable, pero en el panel del menu me 
 carga las tildes correctamente y a la derecha me las carga como un rombo con 
 interrogación. Manejo Firefox y probe cambiando la configuración de 
 caracteres de UTF-8 a Occidental, pero a la izquierda se ve mal y a la 
 derecha se ve bien.
 Si modifico en el codigo por ó ahi se ve bien, pero en otros combos no... 
 como puedo hacer que en ese tpl se vea bien sin modificarlo desde el codigo.

Hola, Lorenita;

También ofrecemos una lista de correo en español. Usted puede
encontrar aquí:

http://php.net/mailinglists

-- 
/Daniel P. Brown
Network Infrastructure Manager
http://www.php.net/

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

[PHP] problem compiling 5.3 with postgresql

[Jim White]

I am having problems compiling 5.3.? with postgresql support.

'./configure' '--with-apxs2=/usr/local/apache2/bin/apxs' 
'--with-pdo-pgsql=/usr/local/postgresql-9.0.3' 
'--with-pgsql=/usr/local/postgresql-9.0.3'


This configure works with 5.2.?, but 5.3.? gets this

ext/standard/.libs/dns.o: In function `php_parserr':
/usr/local/php-5.3.5/ext/standard/dns.c:418: undefined reference to 
`__dn_expand'


and more lines like the last one.

How can I fix this? I am using Ubuntu 10.10.

JIm



--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] Re: PHP session replication

[Alessandro Ferrucci]

Hi Florin, thank you for your write up, actually the main reason why I asked
the original question was because I mainly write servlet based webapps
currently but I've decided to use PHP for my next project mainly for
exploratory reasons.

On Sat, Mar 19, 2011 at 10:06 AM, Florin Jurcovici 
florin.jurcov...@gmail.com wrote:

 Hi.

 Just for comparison:

 PHP does not provide sessions in the same way a servlet-based platform
 provides. PHP actually destroys the in-mem representation of sessions
 after each request is served, whereas a servlet-based platform caches
 the sessions in mem between requests.

 ASP.Net also serializes session state, but not into a cookie - it uses
 a hidden field instead. Which works around cookie size limitation. You
 don't even have a choice of database sessions with ASP.Net. OTOH, even
 if performance might suffer, scalability, as far as the sessions
 mechanism is concerned, is excellent - you don't need session
 replication.

 Servlet-based platforms provide the most complicated solution, when
 compared to the other two. They keep sessions in mem, which improves
 performance (no serialization/deserialization for each request), but
 creates potential scalability problems. You won't hit the wall at a
 few thousands of users, but replicating maybe a million sessions among
 no more than a hundred servers causes the replication process to
 consume quite a lot of resources, the resources being used for
 replication increasing faster than linearly with each added server
 (not quite exponentially, though). You can use sticky sessions with
 most servlet-based platforms, but these come with their own problems
 (already described by a previous poster). Nevertheless, in mem
 sessions a la servlets are a very convenient mechanism to use - the
 session replication is provided by the platform, and the app
 programmer doesn't have to worry about it.

 All three approaches rely on every piece of data in the session being
 serializable, so you can't store interesting objects, like an open
 file or the like, in sessions.

 Does anybody know of any fundamentally different session
 sharing/replication mechanism?

 br,

 flj

 --
 PHP General Mailing List (http://www.php.net/)
 To unsubscribe, visit: http://www.php.net/unsub.php




-- 
Signed,
Alessandro Ferrucci