My only concern is that "Callback" doesn't impress itself as the core of the
system, which is what it is. While I agree, RPC does little in that
department as well, it might seem like there is a better/bigger name we can
find for it.

I don't have any particular affinity towards RPC, so what we come up with
could be a suitable replacement would be fine provided it does a few things:

- distinguishes itself from other namespaces (like like the front
controller)
- is a name that is both abstract enough, yet descriptive enough to be
both a distinguishable and core component of the Zend_Tool suite
- does not describe a particular implementation, but more of a pattern.


Other names I've pondered:
Zend_Tool_System - (too abstract)
Zend_Tool_CallSystem - (this might be ok)
Zend_Tool_Core - (too abstract)
Zend_Tool_Executor - (too technical?)
Zend_Tool_Extender - (?)
Zend_Tool_Framework - (PHPUnit does something similar, so this might make
sense)

-ralph




On 10/17/08 10:22 AM, "Matthew Weier O'Phinney" <matthew@...> wrote:

>
>
>
> -- Tobias Gies <tobiasgies@... <mailto:tobiasgies%40googlemail.com>
> > wrote
> (on Friday, 17 October 2008, 02:19 PM +0200):
>> good point. The first thing that came to my mind when thinking about your
>> message was calling the namespace "Zend_Tool_ProcedureCall" or just
>> "Zend_Tool_Call", because that's what describes best what it does. The
>> current
>> Endpoints of Zend_Tool_Rpc are all procedure calls, whether they are invoked
>> from a remote point or the CLI.
>
> Zend_Tool_Callback may make sense, as well -- because in essence, all
> executable items are PHP callbacks.
>
>> 2008/10/17 Wil Sinclair <wil@... <mailto:wil%40zend.com> >
>>
>>
>> There has been some disagreement on the ZF team at Zend about whether
>> Zend_Tool_Rpc is a good namespace. The following arguments have been put
>> forth:
>>
>> Pro: It was modeled after an RPC interface and looks like an RPC
>> interface, therefore the namespace is appropriate.
>>
>> Con: While some endpoints may expose an RPC interface, not all do. Many
>> endpoints, such as CLI, would use the interface locally. The namespace
>> therefore may lead to confusion about the architecture of the system.
>>
>> We'd like to go with the name that is the representative and clear, so
>> we thought we'd run a small survey in this group. So what do y'all
>> think?
>>
>> ,Wil
>>
>>
>>

--
Ralph Schindler
Software Engineer | ralph.schindler@...
Zend Framework | http://framework.zend.com/