JIMSMITH

Damn! You are awesome.

I use the indy tidtcpserver with the readbytes method. The code is ReadBytes(Buffer,buffsize, False). The buffsize is set for 1024. I receive varying amounts of data say 7000 bytes. After 6 passes I receive an timeout because ( after the first 6 *1024 = 6144 the last pass only has 7000 - 6144 = 856) only 856 bytes remain and the timeout occurs waiting to fill the buffer. When the timeout happens the bytes appear to remain in the iohandler buffer. The question is what is the best way to get the 6 chunks and the remaining 856 bytes without generating an exception? I prefer to use readbytes because ther could be different types of data other than strings. I hope this make sense and I appreciate assistance in advance.

Please delete this message. Problem solved

Okay. I do create them and can get a connection from a pool. I assume that a criticalsection is not required if doing this.

When accessing executing dbqueries using tFDQuert components in a tidtcpserver event should a tcriticalsection?

Remy are there any good articles on the TIdContext and the TIdServerContext and how to use them and when to use one over the other properly? Thanks in advance.

I am starting to work on this. I always have a high level of confidence in your responses on any topic. Thank you very much.

I want to create a server application that can handle multiple connections, even from the same computer. An important point is that if the client application disconnects from the server I need to be able to reconnect the application to the object in the server for continuity. I can handle the reconnect, I think, but need some assistance in associating the the context with the context or object from the original connection. When does the context get destroyed. Many question and I need help finding answers. Seems like I would have to keep a token or something to send to the server to recognize the repetitious connection for each application connected to the server. Am I correct in this assumption? I wonder how I know the connection that was disconnected if the network connection drops. Should I launch an anonymous thread to read and process the message from the execute event on the server? I am continuing m investigation.

You are correct. This is what I am about to correct. I am getting some good clues from these responses. A response could be sent to the client in xml with Success or fail. Success would have the data and fail would have the extended error details. In the case of the ssl failure trapping the message and logging it to a file on the server and then sending the XML with failure would normally work, but this was a failure on connection so there might not be a client to respond to. Just log it on the server when capturing via the exception handler and just move on so the next client communication happens. This might be what I am looking for.

This is a simple case where the 2 .dll files were not with the executable. The problem was not with the indy components either. The key information that I am looking for is how to manage the middle tier so that when any type of exception happens that the middle tier sends the exception to the client and continues to process other connections. Yes I can do this in the application using try finally and try except blocks. Just not sure how to implement this in a middle tier where I want the exception to be passed back to the client.

I use indy tidtcpserver and client. The other day I had a computer that did not have ssl .dll files which resulted in exception in the middle tier. All processing was disrupted. I just need to send exception back to that client connection and allow the other connections continue to process.

I tried to use Remobjects many years ago. Wasn't much documenrtation or many examples. Any questions took several days to get answers. Anyway I wonder how they handle exceptions so that other users continue to process without disruption..

I have an application that connects a middle tier application that I created all using VCL windows. The middle tier application is accessed VIA tcp using Indy. The client application from many computers can access the middle tier at the same time. The problem I have is how do I harden the middle tier so that if an exception happens the entire middle tier is not hung. I do want the exception message to go back to the respective client, but I need the middle tier to be able to continue processing requests from other users.

Thanks for the information. An interesting read.

Apologies. There are supposed to be commas. I have added. Thanks. I made manual changes to for illustration purposes and make my 1st mistake.