Hi,
I registered my wiki account "Blar" and need some karma for my first RFC
for new cookie functions. I already posted some infos about
"http_cookie_set and http_cookie_remove" on the mailinglist.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
--
Andreas Heigl
andr...@heigl.org
> Am 20.07.2017 um 14:03 schrieb Johannes Schlüter <johan...@schlueters.de>:
>
>> On Do, 2017-07-20 at 14:06 +0200, Niklas Keller wrote:
>> I'm fine with no user registration required, but there should
>> definitely be a
it simple and stupid.
But thats - as I said - just my 0.02€
Cheers
Andreas
PS: As it's a pretty massive change to the infrastructure I'd personally think
there should be an RFC about that.
>
>
>
>
>
>> On 19 July 2017 at 21:12, Andreas Heigl <andr...@heigl.org&
eem to
be "PHP-approved" to people not that deep into the website (so about 99% of
PHP-developers). So the PHP-website would - even though that might not be
intended - recommend frameworks or libraries over others. And we would not want
that!
Just my 0.02 €
Cheers
Andreas
>
On 18.7.2017 21:37, Nikita Popov wrote:
What is the minimum MySQL version we support? can I drop checks for MySQL
3.x and 4.x?
The "oldoldstable" Debian Wheezy from 2013 supports MySQL 5.5. The
unsupported Debian Lenny has MySQL 5.0 since 2009. In my opinion the
next release of PHP no
Hello Andrey,
$options are equal to the optional parameters of setcookie and setrawcookie.
$options may contain:
expires: int
path: string
domain: string
secure: bool
httponly: bool
1. The wording here implies that these are the *only* attributes
allowed. In the interest of
Hi,
i want some feedback, about the following idea before i write a rfc.
Problem:
The functions setcookie and setrawcookie has many parameters. Most of
them are optional and extensions (e.g. same-site) make it even more messy.
The functions setcookie and setrawcookie has 8 parameters.
bool
Hi Michael,
Allow else blocks to follow iteration blocks. The else block is executed
if no iteration occurs for any reason.
I also thought it would been a good idea, but most of the time i need a
wrapper in the output like this:
if($items) {
echo '';
foreach($items as
> PHP already exhibits the skipping behaviour (it only emits a warning
> for the wrong type used in `foreach`, skips the loop, and then
> continues with remaining code).
Yes, a warning is not an error. If someone dont care about warnings from
error prone code, set the error_reporting
Am 04.07.17 um 10:19 schrieb Andreas Treichel:
> Hello,
>
>>> One thing though that I thought about: Chapter 4 of RFC 3062 explicitly
>>> > states that this function should only be available with confidentially
>>> > support like TLS. So p
Hello,
One thing though that I thought about: Chapter 4 of RFC 3062 explicitly
> states that this function should only be available with confidentially
> support like TLS. So perhaps we should check whether the data will be
> transfered via a secure connection and - if not - raise an error?
for the returned value!).
I'd always return the new password. In userland users can compare the
password passed in to the returned password to see whether it was
generated or altered in a way. I think it makes it more consistent than
having to check for three values (FALSE, null|'' a
Hey Andreas.
Am 04.07.17 um 00:16 schrieb Andreas Treichel:
> Hey Côme, hey Andreas.
>
>> string|FALSE ldap_exop_whoami(resource $link) - The returned string is
>> the DN of the currently bound user.
>
> In my opinion the code is really ease to read with exceptions
Hey Côme, hey Andreas.
> string|FALSE ldap_exop_whoami(resource $link) - The returned string is
> the DN of the currently bound user.
In my opinion the code is really ease to read with exceptions.
try {
$user = ldap_exop_whoami($link);
}
catch(Throwable $e) {
}
string
Hey Côme, hey Andreas.
Am 03.07.17 um 17:04 schrieb Andreas Treichel:
> Hello,
>
> please change the signature form
>
> bool ldap_exop_whoami(resource $link, string &$result)
>
> to
>
> string ldap_whoami(resource $link);
>
> i dont see the benefit to r
On Mon, Jul 3, 2017 at 6:08 PM, Andreas Hennings <andr...@dqxtech.net> wrote:
> On Mon, Jul 3, 2017 at 5:53 PM, Johannes Schlüter
> <johan...@schlueters.de> wrote:
>> On Mo, 2017-07-03 at 17:32 +0200, Niklas Keller wrote:
>>
>>> > That distinction is the r
On Mon, Jul 3, 2017 at 5:53 PM, Johannes Schlüter
wrote:
> On Mo, 2017-07-03 at 17:32 +0200, Niklas Keller wrote:
>
>> > That distinction is the reason why next() and valid() are different
>> > methods in iterators.
I would rather say this is the reason why current() and
On Mon, Jul 3, 2017 at 5:27 PM, Johannes Schlüter
wrote:
>
> Wouldn't SPL's NoRewindIterator be enough?
>
> $nit = new NoRewindIterator($it);
>
> foreach ($nit as $row) {
> break;
> }
> foreach ($nit as $row) {
> // continues same iteration
> }
I had not noticed this
On Mon, Jul 3, 2017 at 9:09 AM, Niklas Keller <m...@kelunik.com> wrote:
>
> Hey Andreas,
>
> what you're trying to do here seems to be premature optimization. While you
> save a bunch of method calls, your I/O will be the actual bottleneck there.
> It's entirely fine
Mon, Jul 3, 2017 at 3:42 PM, Sara Golemon <poll...@php.net> wrote:
> On Sun, Jul 2, 2017 at 10:49 PM, Andreas Hennings <andr...@dqxtech.net> wrote:
>> (I wanted dedicated reader classes for different return types, e.g.
>> one "RowReader", one "AssocReader"
With any exception from PascalCase you cannot e.g. generate class names
from strings without a explicit mapping table:
documentElement->tagName;
$className = ucfirst($tagName) . 'Parser';
if (!class_exists($className)) {
throw new RuntimeException('Parser not found for
Hello,
please change the signature form
bool ldap_exop_whoami(resource $link, string &$result)
to
string ldap_whoami(resource $link);
i dont see the benefit to return a single value with a reference.
Without a reference the function can used as an argument:
Well, on a current project I made an attempt to write different
adapters in userland.
I finally decided that the clutter is not worth.
So for this project I wrote everything as "readers", and not as iterators.
With a native solution, one could do this:
function generate() {
yield 'a';
yield
ata", so that FALSE would become a
valid value.
I currently don't see a better option than FALSE.
Maybe a sub-interface of ReaderAggregate can have an method "->getStopValue()",
which would allow to specify something other than FALSE.
- Andreas Hennings
(https://github.com/donquixote)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
The key will simply be a counter.
Open questions:
- The naming of "Reader", "ReaderAggregate", "->read()".
- Which return value to use for "end of data", so that FALSE would become a
valid value.
I currently don't see a better option than FALSE.
- Andreas Hennings
(https://github.com/donquixote)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
- The naming of "Reader", "ReaderAggregate", "->read()".
- Which return value to use for "end of data", so that FALSE would become a
valid value.
I currently don't see a better option than FALSE.
- Andreas Hennings
(https://github.com/donquixote)
wait for PHP 7.3/8.0. As the changes
do not change the language itself but add long awaited features for
LDAP-Interaction I'd love to see this in PHP 7.2
Cheers
Andreas
--
,,,
Hi All.
I'd like to edit the LDAP-EXOP RFC[1]that Côme just created as we'Re
both working on that.
Would it be possible to grant me karma for that?
Thanks and Cheers
Andreas
[1] https://wiki.php.net/rfc/ldap_exop
n EXOP operations out
> there.
As already mentioned on IRC I'm much more in favour of keeping the
naming more simple and use ldap_whoami and ldap_passwd instead of the
ldap_exop_whoami and ldap_Exop_passwd as there is no exop-parameter
necessary. Though we need to add the requirement of the serve
::ISO8601 to that new
constant so the functionality can be kept as-is without much hassle.
Just my 0.02 €
Cheers
Andreas
--
,,,
(o o)
+---
Am 30.05.17 um 11:45 schrieb Côme Chilliet:
> Hello,
>
> Just to be sure, in which branches/versions should a PR like this one get
> merged: https://github.com/php/php-src/pull/2536 ?
>
> Côme
>
IMHO that's a bug-fix, not a security-issue, so master, 7.1 and
--
Andreas Heigl
andr...@heigl.org
> Am 17.05.2017 um 16:28 schrieb Sammy Kaye Powers <m...@sammyk.me>:
>
> Hello internals folks!
>
> As you may already know, run-tests.php is an old legacy app that is in
> serious need of a refactor. Some things that are ba
ine of "As
the extension isn't maintained since there won't be a fix
for this issue. We're therefore closing it now."
Apart from that I'm fine with it :)
My 0.02€
Cheers
Andreas
--
,,,
one…
But as I said: just my 0.02€
Cheers
Andreas
>
> But of course, I don't see it as a must-have, just as nice-to-have.
>
> Cheers,
> Victor
>
> On Thu, Mar 2, 2017 at 4:03 PM Andreas Heigl <andr...@heigl.org> wrote:
>
>> Hi Victor.
>>
>>
o implement in userland I'm
not sure it makes to add them to the core…
But that's just my 0.02€
Cheers
Andreas
--
,,,
(o o)
+-----
ove a feature to edit multiple issues at
once. But that's something for a later stage!
I'm definitely looking forward to seeing that going live in the near future!
Cheers
Andreas
--
,,,
"could"s in there: I'd love
to help out: But someone will need to help me (or whoever else wants to
help) in getting to know the details and internals of – internals? – the
system…
Just my 0.02 €
Cheers
Andreas
--
> Am 14.01.2017 um 11:26 schrieb Fleshgrinder <p...@fleshgrinder.com>:
>
>> On 1/14/2017 11:20 AM, Andreas Heigl wrote:
>> Do we as "makers of PHP" want to dictate the user what the "intended"
>> behaviour of PHP is? Or are we treating the use
But should I limit
all those users with a valid use-case for it just to save some from
missusing it? And if we start with that, where should we stop?
Just my 0.02€
Cheers
Andreas
>
--
,,,
issue is still open, we can easily alter
the PHP-Version within the issue instead of closing it.
For the future an automated mechanism as described earlier would be
awesome. And that would spread the load back onto the reporter as well.
My 0.02€
Cheers
Andreas
--
There might be issues that are still relevant, but IMHO it's easier to
reopen an issue when need arises than investing the manpower of checking
whether that's still an issue w
Am 12.12.16 um 16:26 schrieb Sammy Kaye Powers:
> Hey internals!
>
> As pointed out in Paragon's excellent blog post,
> openssl_public_encrypt() & openssl_private_decrypt() defaults to the
> insecure OPENSSL_PKCS1_PADDING constant.
>
>
Hi Sascha.
Thanks for the clarification. Can you shed some light to whether pb1.php.net -
which according to https://wiki.php.net/systems/pb1 holds the mailinglists - is
still tunning Ecelerity or not?
Cheers
Andreas
--
Andreas Heigl
andr...@heigl.org
> Am 04.12.2016 um 10:41 schr
-solutions for special use-cases.
That might be a feasible solution for the mailinglists but I don't see
our actual Emails going that way.
But perhaps others see that different.
Cheers
Andreas
--
,,,
But *that's* a second step in my eyes.
Let's first handle the beast at hands and then see what comes up next.
Cheers
Andreas
>
> -Rasmus
>
> On Thu, Dec 1, 2016 at 7:46 AM, Andreas Heigl <andr...@heigl.org> wrote:
>
>> Hi All.
>>
>> Looks like there should
t's wnated
that I do that - provide me with insight (and credentials)?
Cheers
Andreas
Am 01.12.16 um 15:40 schrieb Eli:
> Stas ... I think this falls under the whole "no-one really knows who
> handles the mailing stuff".
>
> I myself have an issue that 'randomly' my emails wi
folder...
And then there's also phpenv which took rbenv as a model.
Cheers
Andreas
Am 02.09.16 um 14:28 schrieb Jordan Gigov:
> Most developers who hope to move a site to PHP 7 will still have to
> maintain PHP 5 sites for a long time, requiring the presence of both.
> However, buildi
Am 27.06.16 um 17:41 schrieb Bishop Bettini:
> On Mon, Jun 27, 2016 at 11:31 AM, Andreas Heigl <andr...@heigl.org> wrote:
>
>> Am 27.06.16 um 15:28 schrieb Karl Pflästerer:
>>> Andreas Heigl <andr...@heigl.org> writes:
>>>
>>>> Am 27.06.1
Am 27.06.16 um 15:28 schrieb Karl Pflästerer:
> Andreas Heigl <andr...@heigl.org> writes:
>
>> Am 27.06.16 um 15:01 schrieb Karl Pflästerer:
>>> interface I1 { const C1 = '';}
>>> class C3 implements I1 { const C1 = 'c2';}
>>> $c3 = new C3;
&g
Am 27.06.16 um 15:01 schrieb Karl Pflästerer:
> interface I1 { const C1 = '';}
> class C3 implements I1 { const C1 = 'c2';}
> $c3 = new C3;
> var_dump($c3::C1);
According to https://3v4l.org/jIcs6 it looks like that's intended
behaviour ;)
Che
at the start of a file would be easily to spot.
Just my 0.02€
Cheers
Andreas
[1] www.unicode.org/versions/Unicode5.0.0/ch02.pdf#page=30, Am 31.05.16
um 05:52 schrieb Sara Golemon
. So in that special case it's **not** the same array
anymore. Or did I miss something?
Cheers
Andreas
Am 29.05.16 um 15:13 schrieb Colin O'Dell:
> Hello everyone,
>
> I'd like to introduce a new RFC for your consideration and discussion:
> https://wiki.php.net/rfc/array_change_key
))->foo(new BaseClass()) will fail as the method 'b'
isn't implemented, but it should be according to the interface...
Hope that helps ;)
Cheers
Andreas
--
,,,
o build
the code around that returned value you can't really use.
So in my opinion either return a proper object/type or throw an exception.
My 2 cent
Cheers
Andreas
>
> While a monad sounds cool, it doesn't seem like the necessary language
> infrastructure is there for it at the momen
o be
in.
In all other cases feature-detection (function_exists/extension_loaded
f.i.) should work fine to determine whether the used engine is able to
run a certain function.
And in the end the goal would be to not adapt the code to different
runtine-engines but to adapt the runtime engines to run the co
ttps://wiki.php.net/rfc/adopt-code-of-conduct#constructive_collaboration_guidelines
>
>
> I want this to work, and work together, to get this approved.
>
> cheers,
> Derick
Thank you
eryone knows who voted what.
Personally I'd opt for version 3 where the vote is *anonymous during the
voting period only*. That way no one can be actively influenced on their
vote. In my eyes that would mean that there is not
n technical votes on what way
the language itself develops (which should always be open and as
transparent as possible) and non-technical votes (which can be very
personal and should therefore respect the privacy of the voter).
Cheers
Andreas
--
Am 12.01.16 um 15:53 schrieb Zeev Suraski:
>
>
>> -Original Message-----
>> From: Andreas Heigl [mailto:andr...@heigl.org]
>> Sent: Tuesday, January 12, 2016 4:21 PM
>> To: Eli <e...@eliw.com>; internals@lists.php.net
>> Subject: Re: [PHP-DEV] Re:
ote should definitely be
> public, and not secret.
Definitely!!! And that requires an RFC that - at least in my eyes -
needs a 2/3rd(+1) majority to be accepted *because* it concerns the
future of the community!
Cheers
Andreas
--
,,,
e I'm sure that this is something that affects the whole
RFC-Process and should be put up in a separate RFC and not just be
implemented "en passant" in a few lines of code. And In my eyes, as it's
a change to the RFC-Proc
function test() {
>> A::test();
>> }
>> }
>>
>> $b = new B;
>> $b->test();
>>
You are calling explicitly A::test().
When you call parent::test() everything works as you'd expect it.
Have a look at https://3v4l.org/RCrRd
h
things in future).
Cheers
Andreas
--
,,,
(o o)
+-----ooO-(_)-Ooo-+
| Andreas Heigl
Am 03.11.15 um 20:07 schrieb Andrea Faulds:
> Hi Andreas,
>
> Andreas Heigl wrote:
>> +1 on that solution. Just throwing "host:port" onto something doesn't
>> help anyone. Try that with "www.google.com:443" in your favourite
>> browser. Most will gi
then see that it's not supported.
The only extension I'd see to it would be to check whether someone is
trying that and raising an error in PHP describing that "this format is
not supported! Please use lda
ith the
return type of the functions called but with the way PHP handles
assignements. But without the void return type declaration we can't even
see that the assignment for $a doesn't make sense in the first place.
W
Hi Rainer.
Am 13.08.15 um 16:39 schrieb Rainer Jung:
Am 12.08.2015 um 13:17 schrieb Andreas Heigl:
Hi Rainer.
Am 12.08.2015 um 13:00 schrieb Rainer Jung rainer.j...@kippdata.de:
Hi Côme,
Am 11.08.2015 um 16:58 schrieb Côme BERNIGAUD:
On 2015-08-11 00:36, Rainer Jung wrote:
The current
for
maintaining compatibility with some edge-case usages. So I'm very interested in
your patch to see how we can rech both goals!
In the meantime you can still use the old ext/ldap for the newer PHP-branch
as it should compile without an issue. The newer ext/ldap just removed stuff
;)
Cheers
Andreas
Andreas
--
Andreas Heigl
andr...@heigl.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
the case sensitivity on osx (for hfs) can be
enabled optionally, or?
Case sensitivity is not an issue of OS X but of the underlying Filesystem which
is by default on HFS+ disabled. You can enable case sensitivity by reformating
the partition using case-sensitive HFS+
Cheers
Andreas
--
Andreas
much
more than HTTP. And the internet is so much more than an implementation of that
protocol by any service provider be it google or yahoo or whatnot.
Cheers
Andreas
--
Andreas Heigl
andr...@heigl.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http
) like to get the news delivered to my doorstep
instead of having to pull the relevant information from a web-interface.
Cheers
Andreas
Regards,
--
Rowan Collins
[IMSoP]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
% of the WorldWideWeb who isn't able to
get his tools set up properly. But that's just my 2 arrogant cent.
Cheers
Andreas
--
Andreas Heigl
andr...@heigl.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
like Phabricator?
And why not Jira? Or bugzilla? Or Bitbucket? Or gitlab? or github? or ...
Why not use the existing tools and spend the time lost in such discussions by
instead making these tools awesome?
Cheers
Andreas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe
Am 02.08.2015 um 17:12 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 16:48 GMT+02:00 Andreas Heigl andr...@heigl.org:
Hi Niklas
Am 02.08.2015 um 16:26 schrieb Niklas Keller m...@kelunik.com:
2015-08-02 15:29 GMT+02:00 Rowan Collins rowan.coll...@gmail.com:
On 2 August 2015
that's a good idea in the first place ;)
Cheers
Andreas
Cheers,
Patrick
--
,,,
(o o)
+-ooO-(_)-Ooo
;-).
What's the issue with the name?
As far as I see it, There's no problem at all, as there's UString and
then there's Hoa\UString. Different namespace, no issue.
Or am I missing something?
Cheers
Andreas
Moreover, this library provides an API that is useful for daily use and
can be inspiring
would that be expected behaviour? I mean I can't do
$date = (DateTime) $timestring;
after all, can I? But I can use
$date = new DateTime($timestring);
Just my 2 Cent.
Cheers
Andreas
Hi all.
Am 25.06.15 um 17:56 schrieb Anatol Belski:
Any feedback from the ldap users were appreciated here, as well.
* https://github.com/smalot/ldap uses ldap_sort, issue is raised
* https://github.com/matgou/GorgLdapOrmBundle uses ldap_sort, informed
the maintainer via email
Cheers
Andreas
Hi Anatol.
Côme already replied to the technical aspects of what we are trying to do.
Am 25.06.15 um 17:56 schrieb Anatol Belski:
Hi Andreas,
-Original Message-
From: Andreas Heigl [mailto:andr...@heigl.org]
Sent: Wednesday, June 24, 2015 5:40 PM
To: internals@lists.php.net
Cc
of decission? And will it be possible to get
that marked deprecated in 7 at all?
Thanks for your help in getting this right.
Cheers
Andreas
[1] https://github.com/php/php-src/pull/1357
[2]
http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=include/ldap.h;h
to be listed?
I'd expect an appropriate information at least at
http://php.net/manual/en/ldap.requirements.php
I can do that if you'd like ;)
Cheers
Andreas
--
,,,
(o o
-representation?
That would also allow something like this
function getprice(int $money) {
$money = $money * CURRENT_VAT;
return $money;
}
which would alter the object in question!
Or are we talking about two completely different things?
Cheers
Andreas
Hi Côme.
According to the gophp7-ext project the LDAP module isn't maintained.
(I've just looked it up this morning). See
https://github.com/gophp7/gophp7-ext/wiki/extensions-catalog. Would you
want or consider thinking about taking over?
Cheers
Andreas
Am 21.04.15 um 09:18 schrieb Côme
://3v4l.org/mUeRk in PHP 5.3.2 the behaviour
was still as you'd expect it, in PHP5.3.3 it was as described in the
ticket. So it seems that there has been a change introduced with
PHP5.3.3 that broke the expected behaviour.
Cheers
Andreas
? Suddenly the IP for a valid SID has changed and the
legitimate user gets kicked out. Every half hour. No Attacker needed.
Does that improve things?
Regards
Andreas
--
,,,
(o
...@ohgaki.net
Regards
Andreas
--
,,,
(o o)
+-ooO-(_)-Ooo-+
| Andreas Heigl
) {
doSomethingWithTheException($e);
}
be more what you are talking about?
Regards
Andreas
--
,,,
(o o)
+-ooO-(_)-Ooo-+
| Andreas
)
+-ooO-(_)-Ooo-+
| Andreas Heigl |
| mailto:andr...@heigl.org N 50°22'59.5 E 08°23'58 |
| http://andreas.heigl.org http://hei.gl/wiFKy7
Hello erveryone, i just want to know how to compile and trace PHP engine source
code on Windows.
I need it for my assignment. I've google search it but all i found is how to
build PHP on Windows.
Thank you very much
--
PHP Internals - PHP Runtime Development Mailing List
To
Hello sir/ma'am
My name is andre from Indonesia. I am a student of a university, and i'm doing
my thesis.
I subscribe to this list to look for some help.
Oh by the way, my thesis is about PHP file encryption. So i need to decrypt the
file when it's accessed and before any further processing.
Hello,
i´am using an SLES 10.1 Server with an Apache 2.2.
There´s PHP 5 installed. When i do an dir -o on the php executable, i can
see that php belongs to root.
My questtion is ...
Do PHP run as user root ?
Thanks Andreas
--
PHP Internals - PHP Runtime Development Mailing List
not sure if it's
OK/complete... and I'm not sure if something like that is really needed
in the core (and I'm definetly not the person to decide on that ;-)).
Anyway, I attatched a simple patch against current 5_2 branch to this
mail, perhaps it helps.
Best regards
Andreas
Index
provide it as
an optional compile flag in the configure script?
I think PECL:memcache is the perfect place for such a session-handler.
best regards
Andreas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
... it could implement the 5 functions
from ext/http too, and replace that extension without any BC-issues...
best regards
Andreas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
missing in PHP!
best regards
Andreas
PS: will a 64 bit INTEGER make it into PHP6?
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
timestamps after 2038. Of course, with 64-bit
INTs there was no error to report.
But that's the problem. You need a 64bit integer which is always 64bits
regardless of your platform:
http://www.php.net/~derick/meeting-notes.html#add-a-64bit-integer
regards
Andreas
--
PHP Internals - PHP Runtime
Hi all,
I had posted a patch on 22 Dec for implementing fractional timeouts (by
treating all timeout variables as floats).
Did anyone had a look at it? Any comments?
Cheers,
Andreas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Sebastian wrote:
The PHP soap implementation is very fast by the way ... my benchmarks
indicated 3-4ms request times on the LAN (without doing anything useful
inside the request). This compares to over 30ms for the
mod_perl/Soap::Lite implementation (and I haven't tested Java or .Net)
to the FTP and IMAP code should get looked at for sanity
(probably best by the maintainers).
Best regards
Andreas
diff -Naur php-src-orig/ext/curl/streams.c php-src/ext/curl/streams.c
--- php-src-orig/ext/curl/streams.c 2005-12-22 09:17:40.0 -0500
+++ php-src/ext/curl/streams.c 2005
401 - 500 of 535 matches
Mail list logo