|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #63556 stream_notification_callback
Submitted: 2012-11-18 21:19 UTC Modified: -
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: cameron at datashovel dot com Assigned:
Status: Open Package: Streams related
PHP Version: 5.4.8 OS: FreeBSD9.x
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2012-11-18 21:19 UTC] cameron at datashovel dot com
I've been doing alot of research / experimentation with libevent in PHP recently.

I have been thinking about how I would want to implement an event-based 
framework, similar to reactphp (

I think it would be a nice addition if we had the ability to receive a subset of 
the stream_notification_callback notifications on plain tcp/udp sockets.  This 
way if I create a custom streamWrapper, I can do this in a way that makes it easy 
to hook libevent into my stream implementations.  It appears the only 2 
implementations for these notifications via stream_notification_callback are in 
the http and ftp wrappers.

Test script:
this is an enhancement request, not necessarily a bug.

Expected result:
enhancement, not bug

Actual result:
enhancement, not bug


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2012-11-18 23:07 UTC] cameron at datashovel dot com
One thing I think I should clarify.  Ideally the notifications would work for 
servers as well as clients.  In particular I'm thinking about the 'connect' and 
'close' notifications.  Not sure if the original intention for the notifications 
was to work in both directions, since it appears both implementations are meant 
for clients.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Mon Mar 04 16:01:29 2024 UTC