Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:18809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40846 invoked by uid 1010); 13 Sep 2005 05:07:46 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 40831 invoked from network); 13 Sep 2005 05:07:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Sep 2005 05:07:46 -0000 X-Host-Fingerprint: 65.19.190.98 procata.com Linux 2.4/2.6 Received: from ([65.19.190.98:33754] helo=procata.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 3D/98-62395-1AE56234 for ; Tue, 13 Sep 2005 01:07:45 -0400 Received: from 65.111.204.62 ([65.111.204.62]) by procata.com for ; Mon, 12 Sep 2005 22:07:35 -0700 Mime-Version: 1.0 (Apple Message framework v622) Content-Transfer-Encoding: 7bit Message-ID: <253fbb6f28c5943cfce697c54ace09d0@procata.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: PHP Developers Mailing List Date: Tue, 13 Sep 2005 01:07:47 -0400 X-Mailer: Apple Mail (2.622) Subject: Subject and Observer Interfaces From: jeff@procata.com (Jeff Moore) Would it be possible to remove the Subject and Observer interfaces or at least delay them until a later release? The problem with the Observer interface is that any class implementing it is only capable of receiving one kind of notification (update) and there is no capability to send any additional information. The problem with the Subject interface is that it can also only support one kind of observer. Together these are harsh restrictions that would limit the use of these interfaces to only the most trivial applications. These interfaces are fine as a textbook example of the observer pattern, but I don't see them as generally useful enough to have as part of the language. Regards, Jeff Moore