bayeux4netty suggestions

[Dai Jun]

HI Bob,

On Wed, Sep 2, 2009 at 8:44 AM, Bob McWhirter<bmcwhirt at redhat.com> wrote:
>>> I'd ultimately like a router.send(PublishRequest r) or
>>> router.send(BayeuxData m), plus a List<X> form of those.
>>
>> Would PublishRequest... and BayeuxData... (varargs) also be useful?
>
> I think List<X> suffices for my immediate use-case.

Thanks for you suggestions. En, List is very required and I will add
it very soon. I think varargs is very useful to avoid initialize List,
when just sending 2-3 messages. And it's also interesting to
Javascript developers. We could implement it in future.

>
>> Another thing Bob and I discussed about naming was receiveToQueue()
>> and
>> sendToQueue() in BayeuxConnection.  Perhaps they could be renamed to
>> something more comprehensive, like offerUpstreamEvent() and
>> offerDownstreamEvent() for example.  I guess we need some
>> brainstorming, Bob and Danny?
>
> I'm a tad too ignorant to chime in just yet.

Not at all. You're very welcome!

>
>        -Bob
> _______________________________________________
> netty-dev mailing list
> netty-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-dev
>


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
Samuel Goldwyn  - "I'm willing to admit that I may not always be
right, but I am never wrong." -
http://www.brainyquote.com/quotes/authors/s/samuel_goldwyn.html