Comments inline
On Sun, 2007-09-09 at 13:07 -0400, Ilia Alshanetsky wrote:
> Its been about a week since RFS for features to go into 5.3 has gone
> out and while there was not a "flood" of ideas there is a substantial
> list of key changes people would like to go into this release. I've
> co
Keep-alive support in SOAP is often problematic as most SOAP frameworks
were originally developed under the assumptions that the SOAP HTTP
binding would be HTTP 1.0, which is no longer the case.
Since RPC SOAP operations are not like document downloading in the
strict HTTP sense, frameworks have
On Sat, 2006-05-20 at 17:27 -0400, Wez Furlong wrote:
> On 5/20/06, Al Baker <[EMAIL PROTECTED]> wrote:
> > Are there any plans for upgrading the SQLite driver?
>
> Yes. We didn't want to do this in a point release of PHP because of
> BC concerns.
I think moving t
Hi,
While working on a large embedded project using PHP and SQLite, I ran
into some compatibility issues where the sqlite guys broke file
compatibility on a dot release.
The SQLite situation is:
- SQLite 3.3.x can read and write any SQLite 3.x file
- SQLite 3.2.x cannot work with SQLite 3.3.0+ f
default to something rather than
segfaulting.
Regards,
Al
On Fri, 2006-03-17 at 02:28 -0500, Al Baker wrote:
> Hi,
>
> We're trying to run php 5.1.2 on Windriver Linux (PPC) -- unsupported I
> know -- and most things appear to be working. However when trying to
> use S
Hi,
We're trying to run php 5.1.2 on Windriver Linux (PPC) -- unsupported I
know -- and most things appear to be working. However when trying to
use Smarty (which has calls to date functions for caching), PHP
segfaults in time().
Running PHP in GDB shows the trace of failing in memcpy and malloc
Generally speaking, many users want to be able to catch every error
possible. If there is an error condition that happens, they want to be
able to catch it.
If it's not possible to catch it in script, perhaps an extension or some
other strategy needs to be documented for certain error conditions.
I agree with Ilia that removing these would help drastically reduce the
security holes present in PHP applications and generally improve the
image of PHP security. Or an alternative way to say that, is it would
reduce the FUD being slung at PHP from ignorant people saying PHP is a
security nightma
is YANP sans the import feature as defined in
Jessie's proposal.
Thanks!
Al
On Fri, 2005-07-08 at 20:25 -0400, Al Baker wrote:
> I think we're trying to boil the ocean here, and in doing so failing to
> see both the problems that need to be solved, and the possible
> solutions. I
I think we're trying to boil the ocean here, and in doing so failing to
see both the problems that need to be solved, and the possible
solutions. I'd like to break things down a little bit here to address
what the real problem is with a lack of namespaces in PHP.
In my eyes, there are really only
Parameter validation is a general thing done for security, whether that
be if you're using a variable in an include, database credentials,
connecting to a web service, etc. You need to make sure that those
basic conditions have a highly controlled set of values, not only for
security but to make s
I think it means being able to scope the default execution block for a
script. Normally script goes from top-to-bottom dipping into each
include and compiles and executes them in a linear fashion.
Perhaps having a main would hold off on the execution part until you got
to the main() and from ther
There is nothing wrong with fopen or include, and PHP isn't
instrinically broken here. The only thing intrinsic about PHP that has
anything to do with these security areas is how PHP is powerfully simple
- lowering the bar for adoption. When you do this, you pick up newbie
programmers who code up
-8, SJIS, as was the detect_order.
- the http_output ini setting was set to pass in the ini file, and
mb_output_handler is used at run-time with the preferred encoding
(either UTF-8 or SJIS)
- substitute character and function overloading are both off/disabled
Any suggestions?
Thanks,
Al Baker
s in memory. A high performing mechanism to keep
variables in memory, persist objects between requests, and serialize
objects for use in multiple scripts is essential in my opinion. Also,
how would this play with JSR-223?
Regards,
Al Baker
On Thu, 2004-10-21 at 23:45 +0100, Wez Furlong wrote:
ound 94 entries as you said?
>
>
> and, aside from this issue, I found the encoding related bug
> again (sigh...)
>
> http://bugs.php.net/bug.php?id=29518
>
> how do you think about this? it's worth fixing? or you think this
> is just a bogus one?
>
>
&g
There's nothing stopping someone from writing their own classes for
dispatching and handling events and implementing callbacks today...
Are you suggesting something built into PHP like the Java system event
queue that people can define their own dispatchers and handlers for?
The QT example below i
ell me the id of the bugs you mentioned? as I
> stated, I always take care not to do any harm to the other codes, so
> of course I'll fix them ASAP if it's caused by my option.
>
> regards,
> Masaki Fujimoto
>
> The Message From Al Baker on Mon, 30 Aug 2004 15:1
alization" as a _new_ feature of PHP 5...
> >Has there been big changes to the way PHP5 handles i18n?
> >
> >[1] http://www.zend.com/zend/zend-engine-summary.php
> >
> >Thanks,
> >Adam
> >
> >On 30/08/2004, at 2:11 PM, Derick Rethans wrote:
> >
So, all the mb_* functions will have the experimental removed? I see a
few that still have it, or is that just the mirrors not up to date yet?
Al
On Sat, 2004-08-28 at 23:35 +1000, Dave Barr wrote:
> Derick Rethans wrote:
> > On Fri, 27 Aug 2004, Al Baker wrote:
> >
> >
wrote:
> Hi,
>
> On 2004/08/28, at 5:15, Al Baker wrote:
> > I'm trying to find status on the multibyte support in PHP. The manual
> > shows the functions in mbstring to be experimental and it's hard to
> > find
> > evidence of how stable it really
Hi,
I'm trying to find status on the multibyte support in PHP. The manual
shows the functions in mbstring to be experimental and it's hard to find
evidence of how stable it really is.
Is this natively supported in PHP after 4.3.x?
Thanks,
Al
--
PHP Internals - PHP Runtime Development Mailing
I would just like to echo some concerns on namespaces. I've pioneered
the adoption of PHP in some enterprise development groups at Avaya, and
it's been adopted on the merits of the fastest and easiest tool for web
interface development.
Every now and then someone duplicates a class name and mutte
I agree, that's the exact behavior I would like as well and what most
people would expect.
Al
On Wed, 2004-08-11 at 23:52 -0400, Hans Lellelid wrote:
> Alan Knowles wrote:
>
> > I think he's referening to something like this (which is common in pear):
> >
> > $x = $someobj->somemethod();
> > if
24 matches
Mail list logo
