FiveTech Software tech support forums

... then oSocket:bAccept = { | oSocket | oClient := TSocket():Accept( oSocket:nSocket ),; oClient:Cargo := ST_COMMAND,; oClient:bRead := { | oSocket | OnRead( oSocket ) },; oClient:bClose := { | oSocket | OnClose( oSocket ) } } oSocket:Listen() But I was maybe thinking that oSocket:SendData could return ...

... BUT i dont have any other problems. Nothing is crashing. Network on the ce device still works. Ip address renew works. It just wont accept another onRead event. Am i right in assuming 2 sockets are used. The first one is created and listens for a request. When one arrives another socket is created ...

Can I use oSocket:OnRead instead of oSocket:bRead ?

Regards,
Dutch

Dutch, Imagine this example: 1) I tell you to go somewhere and get an envelope for me. 2) You go there, get the envelope and return it to me. 3) Again I ask you to go for a new envelope. etc A common error is: 1) I tell you to go somewhere and get an envelope for me. 2) You go and get the envelope, ...

Dutch,

You should only read data when Windows tell you so, and it tells it to you invoking bRead.

So you should not wait for new data inside OnRead. That is a common mistake because this process is not properly understood.

... data, We will use ::bRead routine. ?? case 2. when expected data, (after we send request *inquiry*) and it will send data back. We will use ::OnRead() ?? case 3. on 2nd case expected data will run to :bRead also? Regards, Dutch PS. In the past, this program run via RS232 (Com port).

Dutch,

bRead is evaluated when new data arrives, then OnRead() reads the arrived data.

So the sequence is:

Event (new data arrives) --> We proceed to read the arrived data --> once all expected data has arrived then you may send an acknowledge

... data but the protocol have to receive data and send ack. The problem is I don't which one will get the data (between oSocket:bRead or oSocket:OnRead())? *--------------------*function Client()   oSocket := TSocket():New( nPort )   oSocket:bRead    = { | oSocket ...

... CLASS TPop3 DATA   lHeaderOnly   // New Data METHOD New()   ::lHeaderOnly:=.F.  // Initialize the Value to .F. In METHOD OnRead() Line 147          if ::lHeaderOnly                    cCommand ...

I made another modification to method OnRead() - Lines 341-345 - so that the attachments are displayed with the proper case and the path is not shown in the mail (some clients did show it cause the full "name=")                     ...

Rick;

I feel the same way. But sometimes you just have to. And when you do, I always try to subclass.

CLASS eMAIL FROM TSMTP
....

In this case I replaced the OnRead Method to include all the other flags.


Reinaldo.

... ) oSocket:bAccept = { | oSocket | oClient := TSocket():Accept( oSocket:nSocket ),; oClient:Cargo := ST_COMMAND,; oClient:bRead := { | oSocket | OnRead( oSocket ) },; oClient:bClose := { | oSocket | OnClose( oSocket ) } } oSocket:Listen() return nil //------------------------------------------------------------------------// ...

... = C < [ 2] = A { ... } Stack Calls =========== Called from: => AT(0) Called from: => CLEANEMAIL(659) Called from: tsmtp.prg => TSMTP:ONREAD(270) Called from: tsmtp.prg => (b)TSMTP:NEW(131) Called from: tsocket.prg => (b)TSOCKET:TSOCKET(77) Called from: tsocket.prg => TSOCKET:ONREAD(0) ...

Tim OK .. I see the OnRead method and I see where to plug in the code .. I will attempt to patch the 8.07 tsmtp and add the TempFile() static function and let everyone know if it works .. Many thanks .. if this works I can re-start ...

I'm using the SMTP extension to the FWH class. Louis provided this extension a number of years ago. In the OnRead( ) method, at least in my version, there is an oSocket:SendData( ) operation for including attachments. Here is the code snippet: For nI := 1 To Len( ::aFiles ) ...