Introduction to Indy （转载）(3)

How Indy is Different

Quick Overview

• Uses blocking calls
• Does not rely on events - Indy has events that can be used for informational purposes, but are not required.
• Designed to be threaded - Indy is designed with threading in mind. Indy can be used without threading however.
• Sequential programming

Details

Indy not only uses blocking calls (synchronous) but it acts as such. A typical Indy session looks like this:

with IndyClient do begin

  Connect; Try

  // Do your stuff here

  finally Disconnect; end;

end;

Other components may look something similar to this:

procedure TFormMain.TestOnClick(Sender: TComponent);

begin

  with SocketComponent do begin

    Connect; try

      while not Connected do begin

      if IsError then begin

        Abort;

      end;

      Application.ProcessMessages;

      OutData := ''''Data To send'''';

      while length(OutData) > 0 do begin

        Application.ProcessMessages;

      end;

    finally Disconnect; end;

  end;

end;

procedure TFormMain.OnConnectError;

begin

  IsError := True;

end;

procedure TFormMain.OnRead;

var

  i: Integer;

begin

  i := SocketComponent.Send(OutData);

  OutData := Copy(OutData, i   1, MaxInt);

			   
			   

                       标签：
                   
                   
版权申明：本站文章部分自网络，如有侵权，请联系：west999com@outlook.com

特别注意：本站所有转载文章言论不代表本站观点，本站所提供的摄影照片，插画，设计作品，如需使用，请与原作者联系，版权归原作者所有