Combining Lesson 6 and and QuickStart Client Upload project failed

[dpcroghan]

I am a new RTC SDK user trying to make a project with
1) a client application that will upload or get a file from a server and
2) a server that will listen for Put and Get requests.

For now I would be satisfied to get it working using localhost. I began with the QuickStart ClientUpload project and it worked. To it I added a TrtcDataRequest component and set it up for get requests using the web lesson 6 (client to get a file from any web server). To write the file to disk I looked at the code in the Demos\File_Client project. To the server project I added a TrtcDataRequest component and set it up to listen for get requests.

The puts still work fine but I get no response from the server for the get. I added debug messages and the CheckRequest event of the getfile datarequest object is never accessed. The server onListenError and OnInvalidRequest also do not fire. My URL from the client to the server is simply localhost/mytestfilename.txt. Is this incorrect perhaps for a get request?


Could anybody take a quick look at my sample project and maybe see what I am doing wrong?

Thank you

[D.Tkalcec (RTC)]

1. Have you connected the RtcDataProvider component to RtcHttpServer component (Server property)?
2. Have you assigned a value to the Port property of the RtcHttpServer component?
3. Have you called Liste on the RtcHttpServer component?

To get basic understanding of the RTC SDK, please go through all QuickStart lessons.

Best Regards,
Danijel Tkalcec

[dpcroghan]

Thank you Danijel. I will go through the Quick Start lessons again, especially in regard to the RTCDataProvider.

[dpcroghan]

I succeeded getting my test project working for Gets and Puts. I was wondering what would be the best way to encode a subdirectory name to put the file in or get the file from? Should this just be appended to the file's name in the URL?

Thanks!

[D.Tkalcec (RTC)]

That depends on your design goals. If you want to make it easy for someone to access files through a Web Browser, you can use part of the URI as relative path from documents root. Just make sure there are no special characters used (like "..") and check that the absolute path is really inside the folder where the user has access to.

Best Regards,
Danijel Tkalcec

[dpcroghan]

The files will be created and moved programmatically (via the HTTP Gets or Puts) as part of a site's daily work flow in a Delphi application. Each office has satellite locations with each they need to exchange data asynchronously. Each location has a siteID which could also be the subfolder name from the document root. Once the files are local they will be processed. Given these design goals would you consider other options for specifying a subdirectory name?

Thank you Danijel,
Ric

[D.Tkalcec (RTC)]

There are several "locations" where you can send the file path through:

1) As part of the URI, directly in the Request "FileName" portion (before parameters) or as Query paramters. Sending file paths inside the URI is fine, as long as your paths don't start getting too long. Some proxies have limitations in how long an URI may be and might either refuse forwarding your request, or forward only part of it when the limit is exceeded.

2) As a custom HTTP header value. Sending paths inside HTTP header variables is not something I would recommend, but it should work, as long as you encode the data properly.

3) As part of the request content body. Sending the data in request content body is probably the cleanest solution, you need to use a format which is flexible enough to hold any other information required

Now, it is up to you to decide.

Best Regards,
Danijel Tkalcec

[dpcroghan]

Perfect, thanks.