Re: [xSocket-develop] xSocket SPI interface

[Gregor R. <gre...@go...>]

Hi,

currently only a SPI for the connection package exists. The reason to
separate the SPI for connection and datagram-oriented communication is that
an all-in-one SPI interface would be too inflexible (the datagram one would
be much smaller, because it doesn't have to handle connection-related issues
such like connection timeouts). A SPI for the datagram hasn't been required
yet. Do you need such an SPI? Doesn't the xSocket datagram implementation
work for you?

I wrote an article last year about NIO server architecture which fits very
well with xSocket (
http://today.java.net/pub/a/today/2007/02/13/architecture-of-highly-scalable-nio-server.html).
It is focused on connection-oriented communication, but the core
architecture (dispatcher & worker pool) is the same for the datagram and
connection-oriented approach. Unfortunately a xSocket datagram tutorial
doesn't exits. xSocket is still looking for code and doc contributors.

Cheers
Gregor



2008/2/4, Yuriy Cherniavsky <yur...@gm...>:
>
> Hi Gregor.
>
> I try wrote some test datagram application with xSocket, and was really
> surprise that SPI interface includes only for connection package.
> What is the reason for such architecture?
>
> Yet one question, does exist any architecture diagram of xSocket
> framework?
> It be very comfortable to start from :-)
>
> Truly yours, Yuriy.
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> xSocket-develop mailing list
> xSo...@li...
> https://lists.sourceforge.net/lists/listinfo/xsocket-develop
>