bayeux4netty suggestions
Dai Jun
guiwuu at gmail.com
Sun Sep 27 03:56:10 EDT 2009
Hi,
2009/9/3 Luís M. Costa <luis.m.costa at gmail.com>:
>
> Hi,
>
> Just a quick note to say that I'm totally in favor of a more flexible
> routing mechanism.
>
>
> Danny Dai wrote:
>>
>> Sounds cool! discussed names with Luís M. Costa before. Now, these
>>
>> names are really very hard to understand. IMHO, the word "Event" may
>>
>> imply that methods return event objects, like BayeuxRequestEvent. But
>>
>> the queues only contain and return Bayeux message entities, which is
>>
>> not like events. So, I have a simple rename proposal in below:
>>
>> receiveToQueue -> putToUpstreamQueue
>>
>> sendToQueue -> putToDownstreamQueue
>>
>> pollFromUpsream -> getFromUpstreamQueue
>>
>
> I belive a more intuitive form would be using the get/put prefixes +
> Input/Output + Message, such as:
> receiveToQueue -> putInputMessage
> sendToQueue -> putOutputMessage
>
> pollFromUpsream -> getInputMessage
> or, more simply:
> receiveToQueue -> putRequest
> sendToQueue -> putResponse
>
> pollFromUpsream -> getRequest
> Eventually with “Message” as sufix.
>
> Just a thought,
> Luís M. Costa
> --
> View this message in context: http://n2.nabble.com/bayeux4netty-suggestions-tp3563352p3573134.html
> Sent from the Netty Developer Group mailing list archive at Nabble.com.
>
> _______________________________________________
> netty-dev mailing list
> netty-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-dev
>
Considering importance of upstream/downstream in Netty, I keep the
word and simplify like below:
receiveToQueue -> putToUpstream
sendToQueue -> putToDownstream
pollFromUpsream -> getFromUpstream
Do you like them?
--
Best regards,
Dai Jun or Danny Dai(in English) - http://guiwuu.googlepages.com
GTalk: guiwuu at gmail.com | QQ: 93409048 | MSN: guiwuu at hotmail.com |
Twitter: @guiwuu
Sent from Beijing, 11, China
Pablo Picasso - "Computers are useless. They can only give you
answers." - http://www.brainyquote.com/quotes/authors/p/pablo_picasso.html
More information about the netty-dev
mailing list