Re: [PECL-DEV] RabbitMQ Extension Naming

hi,

rabbitmq as name sounds like an obvious choice for the extension itself.

About the classes/functions name, if they implement a standard and are
fully compatible with possible other alternatives then I don't think
it should be a problem to keep what you have now.

On Thu, Apr 1, 2010 at 10:18 PM, Pieter de Zwart
<[email protected]> wrote:
> Hey guys,
>
> I am going through the motions of getting the RabbitMQ PHP Extension listed
> in PECL. Now that I have an account (thank you Pierre,) the next item is
> naming. The project is currently named php-rabbit on Google Code for obvious
> reasons, and for reasons just as obvious, that name will not work as part of
> the PECL directory.
> Since the extension is currently compiled into rabbit.so/rabbit.dll,
> ³rabbit² or ³rabbitmq² seem like good potential names. Feedback?
>
> There is one caveat: because RabbitMQ implements the AMQP standard, the
> classes provided by this extension are: AMQPConnection, AMQPQueue, etc... Is
> that a problem? Should they become RabbitConnection, or RabbitMQConnection
> depending on the chosen name?
>
> Thanks,
> Pieter
>



-- 
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org