🚀 go-pugleaf

"Vladimir Stefanovic" <antivari@po.sbb.co.yu> wrote in message
news:433cd755@newsgroups.borland.com...

> I want to use Indy to do the same thing that I
> knew with TClientSocket/TServerSocket:

Indy can do everything TClient/ServerSocket does, and more.

> 1) TClientSocket (ctNonBlocking) sends buffer of data
> (possibly lots of data) to TServerSocket( stBlocking/
> OnGetThread )
>
> 2) TServerSocket receives data in a thread, in nagotiated
> protocol, for example: "buffer_length buffer"
>
> 3) TServerSocket sends back the confirmation to client
> that the operation was successful or not.

Ok so far.

> Which Indy components are the most suitable for that
> (I suppose TIdTCPClient/TIdTCPServer)?

Yes.

> Am I supposed to send data in peaces (buffer portins), then
> look how much data was actually sent, and continue from
> that place like I did with TClientSocket/TServerSocket?

No.  When you write data with Indy, you can write the entire data at one
time, and Indy will internally send it in portions as needed.  As far as
your own code is concerned, whichever writing method you call will not
return control to your code until the specified data is passed to the socket
in full.

> The same was with server.

Likewise, when you read data with Indy, you tell Indy how much to read, and
it waits until all of the data is received in full before then returning
control to your code.

> I remember that even in TClientSocket I had SendText()
> which was not reliabe because noone can guarantee that
> *all*  the buffer will be sent at the same time.

That is true, although SendText() does return how many bytes were sent, so
that you can call SendText() with the remaining string data if needed.

> Is the same here?

No.  When you call Indy's Write(String) method, for instance, Write() does
not return until the entire string is passed to the socket in full.


Gambit

"Vladimir Stefanovic" <antivari@po.sbb.co.yu> wrote in message
news:433cd755@newsgroups.borland.com...

> Can someone show some working code?

A better thing to do would be for you to show your original
TClient/ServerSocket code so that someone can then show you how to translate
it into Indy code.


Gambit

Thank you.

-- 
Best regards,
Vladimir Stefanovic 

> A better thing to do would be for you to show your original
> TClient/ServerSocket code so that someone can then show
> you how to translate it into Indy code.

Ok, I'll post my TClientSocket/TServerSocket code
tomorrow, because now I'm in a great hurry (must go to
Belgrade airport to wait for my uncle from Canada).

P.S.

I subscribed yesterday to: news.atozedsoftware.com / *indy*,
and I saw that you are prety frequent there. Have you took
part in creation of Indy?




-- 
Best regards,
Vladimir Stefanovic 

"Vladimir Stefanovic" <antivari@po.sbb.co.yu> wrote in message
news:433ced70@newsgroups.borland.com...

> I subscribed yesterday to: news.atozedsoftware.com / *indy*,
> and I saw that you are prety frequent there. Have you took
> part in creation of Indy?

I am a member of Indy's development and administration teams.


Gambit

>> Can someone show some working code?
>
> A better thing to do would be for you to show your
> original TClient/ServerSocket code so that someone
> can then show you how to translate it into Indy code.

Hi,


This is one of the imaginary scenarios that I want to
port to Indy.

1) CLIENT: Sends request (buffer of data) to SERVER
2) SERVER: Receives request (buffer of data) from CLIENT
3) SERVER: Processes the received buffer of data and
prepares a response
4) SERVER: Sends response to CLIENT of the processing success
5) CLIENT: Receives response from SERVER and shows the message

For example, this should check if the file exists on the server
machine (by the logic of TClintSocket/TServerSocket):

1) CLIENT SENDS BUFFER: buffer_size ASK C:\Autoexec.bat
2) SERVER RECEIVES BUFFER: ASK C:\autoexec.bat
3) SERVER RESOLVES 'ASK' COMMAND AND SERACHES FOR FILE:
FileExists("C:\\autoexec.bat)" AND PREPARES RESPONSE
4) SERVER SENDS BACK BUFFER: buffer_size MSG File exists!
5) CLIENT RECEIVES BUFFER: MSG File exists! and shows the
message "File 'autoexec.bat' exists on server machine".

This is how whould I do it with TServerSocket/TClientSocket
(CLIENT: ctNonBlocking, SERVER: stThreadBlocking):

[I attached Both CLIENT&SERVER CODE & EXE's in the
Attachments group]

I wanted to place the code directly here but unfortunately,
the working code appeared to be too big for the message body.
If you still think that I should place it here, I'll do that.



-- 
Best regards,
Vladimir Stefanovic