tcljava-dev

[tcljava-dev] Socket stuff - good time to improve?

[Neil M. <ne...@cs...>]

Hi all,

OK - my exams are over, and I have some time to look again at my socket
code in Jacl. It needs some work. After the messages a while ago about
common functionality in the Channel class, is now a good time for me to
review the socket code and try and finish it off? i.e. - is the Channel
class in a finished state? Also, what is the model for integrating with
fconfigure, fileevent etc? Has work begun on fileevent?

Cheers,

Neil.

PS - has anyone used my socket code? If so, could you send me feedback
on whether it works as expected, etc?

Re: [tcljava-dev] Socket stuff - good time to improve?

[Mo D. <su...@ba...>]

On Tue, 29 Jan 2002 13:27:59 +0000
Neil Madden <ne...@cs...> wrote:

> Hi all,
> 
> OK - my exams are over, and I have some time to look again at my socket
> code in Jacl. It needs some work. After the messages a while ago about
> common functionality in the Channel class, is now a good time for me to
> review the socket code and try and finish it off? i.e. - is the Channel
> class in a finished state? Also, what is the model for integrating with
> fconfigure, fileevent etc? Has work begun on fileevent?

Well, the socket code is a bit different now. I have rewritten much of
it as part of the Channel rewrite. I don't think there is any reason for
you to hold off on touching up the Socket classes. The fileevent stuff
is going to have to wait until later since it will have to be part of
the Channel rewrite (which is not yet done). If you are looking for
something to do, there are always regression tests. Many current
fail since the test suite was moved up the Tcl 8.3 and Jacl needs to
be updated to match these test cases.

> PS - has anyone used my socket code? If so, could you send me feedback
> on whether it works as expected, etc?

I tested it out for some simple things and it seems to work well. I also added
some more error checks to act more like Tcl and pass more io tests.

cheers
Mo

Re: [tcljava-dev] Socket stuff - good time to improve?

[Neil M. <ne...@cs...>]

Mo DeJong wrote:
> 
> On Tue, 29 Jan 2002 13:27:59 +0000
> Neil Madden <ne...@cs...> wrote:
> 
> > Hi all,
> >
> > OK - my exams are over, and I have some time to look again at my socket
> > code in Jacl. It needs some work. After the messages a while ago about
> > common functionality in the Channel class, is now a good time for me to
> > review the socket code and try and finish it off? i.e. - is the Channel
> > class in a finished state? Also, what is the model for integrating with
> > fconfigure, fileevent etc? Has work begun on fileevent?
> 
> Well, the socket code is a bit different now. I have rewritten much of
> it as part of the Channel rewrite. I don't think there is any reason for
> you to hold off on touching up the Socket classes.

Excellent. I'll start that now then.

> The fileevent stuff
> is going to have to wait until later since it will have to be part of
> the Channel rewrite (which is not yet done). If you are looking for
> something to do, there are always regression tests. Many current
> fail since the test suite was moved up the Tcl 8.3 and Jacl needs to
> be updated to match these test cases.

OK - I'll have a look. Any particular areas to focus on?

> 
> > PS - has anyone used my socket code? If so, could you send me feedback
> > on whether it works as expected, etc?
> 
> I tested it out for some simple things and it seems to work well. I also added
> some more error checks to act more like Tcl and pass more io tests.
> 
> cheers
> Mo
> 
> _______________________________________________
> tcljava-dev mailing list
> tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcljava-dev

Re: [tcljava-dev] Socket stuff - good time to improve?

[Neil M. <ne...@cs...>]

Neil Madden wrote:
> 
> Hi all,
> 
> OK - my exams are over, and I have some time to look again at my socket
> code in Jacl. It needs some work. After the messages a while ago about
> common functionality in the Channel class, is now a good time for me to
> review the socket code and try and finish it off? i.e. - is the Channel
> class in a finished state? Also, what is the model for integrating with
> fconfigure, fileevent etc? Has work begun on fileevent?

I've looked at the new async I/O in Java 1.4, and I think it will be
much more useful than the current synchronous Java I/O (reminds me quite
a lot of a long-winded way of doing what Jacl does for I/O anyway).
However, the calls and classes involved are completely different (for
both async and synchronous I/O). So, how should I go about this? I think
I'm going to try and implement asynchronous I/O just using the current
stuff and Threads for the time being, and then I can think about 1.4. I
think the best way to get 1.4 IO would be to use conditional execution
to decide which SocketChannel implementation to load, as it would
probably have to go into a separate class (it's a rewrite of the entire
thing for the new APIs). Is anyone thinking of using the new APIs for
file IO?

Thoughts?

> 
> Cheers,
> 
> Neil.
> 
-- 
package require Tkhtml;package require http;pack [scrollbar .vsb \
-orient vertical -command {.html yview}] -side right -fill y;pack \
[html .html -bg white -yscrollcommand {.vsb set}] -fill both -expand 1
set t [http::geturl http://mini.net/tcl/976.html];.html parse \
[http::data $t];http::cleanup $t

Re: [tcljava-dev] Socket stuff - good time to improve?

[Shawn B. <sh...@qc...>]

Neil Madden wrote:

>Neil Madden wrote:
>
>>Hi all,
>>
>>OK - my exams are over, and I have some time to look again at my socket
>>code in Jacl. It needs some work. After the messages a while ago about
>>common functionality in the Channel class, is now a good time for me to
>>review the socket code and try and finish it off? i.e. - is the Channel
>>class in a finished state? Also, what is the model for integrating with
>>fconfigure, fileevent etc? Has work begun on fileevent?
>>
>
>I've looked at the new async I/O in Java 1.4, and I think it will be
>much more useful than the current synchronous Java I/O (reminds me quite
>a lot of a long-winded way of doing what Jacl does for I/O anyway).
>However, the calls and classes involved are completely different (for
>both async and synchronous I/O). So, how should I go about this? I think
>I'm going to try and implement asynchronous I/O just using the current
>stuff and Threads for the time being, and then I can think about 1.4. I
>think the best way to get 1.4 IO would be to use conditional execution
>to decide which SocketChannel implementation to load, as it would
>probably have to go into a separate class (it's a rewrite of the entire
>
Agreed. You have to maintain compatibility with Java 1.1/1.2/1.3.

>
>thing for the new APIs). Is anyone thinking of using the new APIs for
>file IO?
>
>Thoughts?
>
>>Cheers,
>>
>>Neil.
>>

-- 
-Shawn Boyce
 QCOM, Inc.   
 Quality Software is Our Business
 http://www.qcominc.com