RTC Forums

Looking forward to learning more about 'RTC-DS'....  is there anything more you can tell us at this time?

Walter

The idea behind RTC DS (RealThinClient DeltaSource) is to provide a set of components which would give you a standardized way for working with remote databases without binding you to a specific in-memory storage component on the Client side or a specific set of direct database access components on the Server side.

Best Regards,
Danijel Tkalcec

Danijel,

How close is the RTC-DS to being released?  Is there a beta group I could join?

Thanks,

Greg

I can't say how close or far RTC DS is to being released (especially since "close" is a relative term), but there will be a public announcement on these Forums once RTC DS is ready for beta testing.

Best Regards,
Danijel Tkalcec

Just to clarify, RTC-DS would be a solution only viable if both the client and the server were Delphi/RTC applications, correct?  If so, it would not be an approach to use in an environment with heterogeneous clients.


Kevin

That is correct. RTC DS is going to be an additional layer on top of the RTC SDK (using RTC remote functions) with the purpose to allow you to easily use TDataSet descendant components in Delphi to communicate with a Database located on the Server. The same functionality can already be achieved directly through RTC remote functions with a bit of coding and any in-memory DataSet implementation.

But ... if you are looking for something to work with heterogeous systems, you are better off using the RTC SDK directly, either by utilizing RTC remote functions over XML-RPC (or JSON - once it is implemented), or by using RTC DataProvider components.

Best Regards,
Danijel Tkalcec

Thanks for bringing this up... I was thinking it would also help package things up at the server in a standard way and could be consumed via REST interface or through client vcl.

You can do this with the RTC SDK already, you do NOT need to wait for RTC DS to package things in a standard way. The only purpose of RTC DS is to simplify things when the Client is written in Delphi.

Best Regards,
Danijel Tkalcec

Yes... I understand.  But originally I was thinking the RTC DS was going to add this ability... and if it was going to have this ability and was going to be released very soon why re-invent the wheel.  But this isn't the case... RTC DS doesn't do this so I'll roll my own if RTC becomes my product of choice for this. 

Just for the info ... I've renamed "RTC DS" (RealThinClient Delta Source) to "RTC DBA" (RealThinClient DataBase Access). I hope the new name will better suit the purpose of the components (once released).

Best Regards,
Danijel Tkalcec

I would just go with RTC DA (Data Access).  Same effect, but a little more encompassing than "Database".

--
Kevin Powick

I think "Data Access" is a bit too general, just like "Delta Source" was. I also think that it can't hurt to have "DB" as part of the name for a product whose main purpose will be remote database access.

PS. RTC SDK can be used for "Data Access", but there are no Database-specific components included. RTC DBA is going to fill that space.

Best Regards,
Danijel Tkalcec

No problem.  It's just that when I see "DBA", I automatically think of its most common usage in the IT industry, which is, Database Administrator.  :)

--
Kevin Powick

Since Database Administration will be one of the things RTC DBA is going to be used for, it's not a bad association :)

Best Regards,
Danijel Tkalcec

DBA:). This is not so far away...most the guys I have motivated to use FPC are DBAs...
Mike

Well ... in the end, I've decided to skip the naming part and simply added DB components to the RTC SDK package ("rtcDB.pas" unit - since v4.27).

Best Regards,
Danijel Tkalcec