Hi Mohan,
when using Grizzly, ideally, you shouldn't even care about NIO or AIO
layer (may be just some configuration aspects).
Grizzly provide flexible Filter-based API, which lets you implement
custom network logic.
Pls. take a look at user guide [1] and specifically its Filters section [2].
WBR,
Alexey.
[1]
http://grizzly.java.net/nonav/docs/docbkx2.0/html/grizzly-docs.html
[2]
http://grizzly.java.net/nonav/docs/docbkx2.0/html/filterchain-filters.html
On 01/20/2012 08:35 AM, Mohan Radhakrishnan wrote:
>
> Hi,
>
> This is a question from a beginner. Many times in the past I have
> attempted to write what grizzly already supports but we lack
> experience with writing this type of code. What is the recommendation
> if we want to write NIO or AIO code with java.util.concurrent
> libraries and also cluster two JVM's ?
>
> Can we use grizzly's NIO code and also write and plugin our own custom
> NIO code and cluster two JVM's ? We don't use HTTP. Are there
> recommendations for a large-scale non-blocking socket implementation ?
> We won't be able to write our own cluster code. JGroups ?
>
> Thanks,
>
> Mohan
>
> DISCLAIMER:
> ==========================================================================================================================================================
>
> The information contained in this e-mail message may be privileged
> and/or confidential and protected from disclosure under applicable
> law. It is intended only for the individual to whom or entity to which
> it is addressed as shown at the beginning of the message. If the
> reader of this message is not the intended recipient, or if the
> employee or agent responsible for delivering the message is not an
> employee or agent of the intended recipient, you are hereby notified
> that any review, dissemination,distribution, use, or copying of this
> message is strictly prohibited. If you have received this message in
> error, please notify us immediately by return e-mail and permanently
> delete this message and your reply to the extent it includes this
> message. Any views or opinions presented in this message or
> attachments are those of the author and do not necessarily represent
> those of the Company. All e-mails and attachments sent and received
> are subject to monitoring, reading, and archival by the Company.
> ==========================================================================================================================================================
>
>