When I try to use async sockets in jconsole - I get an error. I assume this is because async sockets need a message pump that is not setup in the jconsole.
~Yuva On Tue, Mar 25, 2008 at 11:38 AM, bill lam <[EMAIL PROTECTED]> wrote: > I think that the documentation suggested you to start a new J server for > each > c++ client. > > BTW if you use jconsole for J server, the overhead is quite small. ymmv. > > Yuvaraj Athur Raghuvir wrote: > > Hello, > > > > Environment: Windows XP ; J6.02 > > > > I have a case where I use sockets to communicate from a C++ Client to a > J > > Socket Server. When I step through, the J interactive session is usable. > > However, when I pump in large amounts of data, the session window is not > > responsive anymore. When I write out a log, I can see that the J > process is > > alive and processing data. > > > > I am using sockets in async mode on the server side purely to support > > interactive use. > > > > In the User Documentation, there is the statement that for these cases: > > "best designed from the ground up to have the GUI part in one execution > > thread or task that is always responsive and the data processing part in > a > > separate thread or task." [1]. > > > > I was not able to locate any lab or description of multi-threaded > > programming in J/Win32 in my quick search. Is there a reference / sample > > code that can help me out here? > > > > Thanks, > > Yuva > > > > p.s: Would it help to have a form/window purely from the perspective of > > having an explicit message pump? > > > > > > [1] http://www.jsoftware.com/help/user/message_pump.htm > > ---------------------------------------------------------------------- > > For information about J forums see http://www.jsoftware.com/forums.htm > > > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
