Woozle Wuzzle
Momentary elation: Channels

If you've been following my lamenting over NIO and SSL then you can probably guess that I've made it to step 5 (acceptance). I had a moment of elation this morning when I found another one of those obscure NIO classes: Channels. Channels does various conversions between traditional IO streams and NIO channels. In theory I could take SSLSocket's getInputStream() and get a ReadableByteChannel. One problem: ReadableByteChannel is not selectable. Oh well, back to the drawing board.

First grieveing and now momentary elation followed by good swift kick in the gut. Doesn't Sun care about the unstable mental state all of this has left me in?!?

Side note: isn't it annoying that there's no interface that describes a selectable, readable / writeable channel? In other words, there's no common way to describe a Pipe.SourceChannel and SocketChannel. Ppfth!

Comments
Comment by alromy at December 7, 2004 12:56 AM

to open achannel on my recever because i need it and thank you for send code channel

 

Comment by farhad at December 28, 2004 04:36 AM

i want to open some channel on my reciever.
thanks a lot

 

Comment by rgrzywinski at December 28, 2004 07:51 AM

I'm going to need a bit more information than that. What is the receiver? Another process, another program, another machine? Who's initiating the communication?

 

Post a comment













Remember personal info?






Creative Commons License Unless otherwise expressly stated, all original material of whatever nature created by Rob Grzywinski and included in this weblog and any related pages, including the weblog's archives, is licensed under a Creative Commons License.