With the exception of basic Proxy and HTTP authentication, which are provided through the "userLogin" property for Clients running on Windows using the WinInet or WinHTTP API ("useProxy=TRUE" or "useWinHTTP=TRUE"), all communication between your Clients and your Servers should be managed using your own implementation, while RTC components ONLY handle the communication in general. This basically means that it is entirely up to you how you want to implement user login and authentication mechanisms in your RTC Applications.
If you are looking for one example of a login/logout mechanism implemented using RTC remote functions, you can check the RTC Messanger Client and Server Demos. Even though RTC Messenger Client and Server Demos do NOT use a Database (because RTC is not a Database-centric component set), if you were planning on using RTC Remote Functions for communication, these Demos will show you how you can handle Client Sessions and implement automatic user login/logout mechanisms when working with RTC remote functions. Please note that this is NOT the ONLY way to handle user authentication, but just one of the possibilities. You can also manually handle Sessions and/or implement different methods to authenticate your users.
PS. When you have a question, please use the search feature of this Forum to check if your question hasn't already been answered before starting a new topic. In addition to providing a platform for asking questions, this Forum also serves as an archive with solutions to most commonly asked questions. For example, entering "login" or "authentication" in the Search box will show you all topics directly related to your question. Here are just a few examples:
1. ->
AutoSessions, AutoSessionsPing & AutoLogin2. ->
Connect, login and post first request3. ->
Database Access Best Regards,
Danijel Tkalcec