Subj : Proxy Service Issues
To   : Drakmir
From : Digital Man
Date : Tue Oct 11 2005 04:51 pm

  Re: Proxy Service Issues
  By: Drakmir to Digital Man on Fri Oct 07 2005 09:46 am

 >   Re: Proxy Service Issues
 >   By: Digital Man to Drakmir on Thu Oct 06 2005 11:27 pm
 > 
 >  >   Re: Proxy Service Issues
 >  >   By: Drakmir to Digital Man on Fri Oct 07 2005 12:38 am
 >  >
 >  >  >   Re: Proxy Service Issues
 >  >  >   By: Drakmir to Digital Man on Thu Oct 06 2005 11:25 pm
 >  >  >
 >  >  >  >   Re: Proxy Service Issues
 >  >  >  >   By: Digital Man to Drakmir on Thu Oct 06 2005 07:44 pm
 >  >  >  >
 >  >  >  > I hadn't seen that one.  I'll take a look at it and see if it works
 >  >  >  > application.  :)
 >  >  >  >
 >  >  >  > That proxy is slow because I removed block read/write since I wasn'
 >  >  >  > was going wrong.  It was the simpliest example I could get to fail 
 >  >  >  > down the computer with it.
 >  >  >  >
 >  >  >  > Thanks again!
 >  >
 >  >  > So, I adapted socktest to read from client.socket instead of console, 
 >  >  > some reason it won't read the input.  I basically just changed the RAW
 >  >  > inkey for the same if logic above (client.socket.data_waiting).
 >  >  >
 >  >  > Is there a socket option that has to be set or something?
 >  >
 >  > Yes, you can't perform I/O on the client's socket descriptor while the BB
 >  > input thread is servicing the socking. You must set console.lock_input to
 >  > before accessing the client's socket directly and set it to to false when
 >  > you're done.

 > The problem with that is when you have a "service", the console object doesn
 > exist.

When run as a service, there is not "input_thread" (the service is expected to
interact with the socket directly), so the locking is not necessary.

                                                  digital man

Snapple "Real Fact" #90:
The average raindrop falls at 7mph.

---
 þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

.