RTC Forums

Hi Danijel,

my server architecture needs to copy everything that comes in in a remote function as param to a new call to another server (some kind of send through function). TRtcRecord.CopyOf doesn't help as it creates a new object, but I need to copy in am existing object.

Any ideas ? or is it always manual ?

Thanks in advance
Helge

I'm sorry, but I do not understand your problem.

Regards,
Danijel

Something like this, where I have code that makes a copy from one RtcRecord to another which already exists

original :


What I thought of is something like

This should do the trick:

procedure TMyObject.MyCall1Execute(Sender: TRtcConnection; Param: TRtcFunctionInfo; Result: TRtcValue);
  ClientModule1.Data.asObject:=Param.CopyOf; // copy the entire "Param" object
  ClientModule1.Param.FunctionName:='MyCall'; // required only if "function name" has to be changed
  ClientModule1.Call(nil);

Regards,
Danijel

thanks, I will try that at once

Let's say I am inside a delayed call and have data to send back to the caller, how would I do that there ? I tried the following, but it raises later on an access violation


I have in the FpNotifyList a list of TRtcRecord, i'm taking the first one from the list and try to create a new copy of the record from it as result for the delayed call.

I'm doing anything wrong here ?

Thanks in adv. Helge

Edit : It works like a charm, the error was something else I forgot to change when I switched from packed records to TRtcRecord

The explanation for the "asRecord" property in the HELP file says:
{ read: Access stored record / write: assign a copy of the source TRtcRecord }
In other words, this line will result in a memory leak:
If you want to assign a copy of pItem:TRtcValueObject to Result:TRtcValue, you can do it like this:
Or, if you KNOW that "pItem" is a TRtcRecord, you can assign a copy to Result:TRtcValue like this:
Either way will be fine and won't result in memory leaks nor Access Violations, provided that "pItem" is safe to be accessed during the assignment.

As for your Access Violation problem, it could be related to the way you are working with your "pData" and/or "FpNotifyList" objects in a multi-threaded environment. If you are simply using a TList which is being populated from a different thread, but are NOT using critical sections anywhere to secure access to that list, you will run into problems when more than one thread tries to access the list at the same time. And I don't see anything in your code snippet which would suggest a use of critical sections.

Best Regards,
Danijel Tkalcec

thanks for the explanation.

to clarify fast : The access violation was my fault, not RTC, it had nothing to do with it, but the way I treated in another code the RtcRecord (before I had a delphi record and this code still used it as such).

pItem is a TRtcRecord, that I send from another thread but never acces it afterwards outside the code I showed. So that should be all good.

this makes the copy and I free pItem directly after, as I don't need it anymore.

this will use my current copy directly and RTC will free it ? So i don't free it myself ?

Thanks :)

Well, not quite. Let me try to rephrase my reply.

The "CopyOf" method creates a copy, as well as an assignment to the "asResult" property, because of which the two lines below basically do the same thing, just in a different way:

If you want to assign the original "pItem" object and NOT a copy of that object (in which case the Result object would manage your object, so you should NOT destroy it yourself), you have to assign your object to the "asObject" property, like this:

What you should NOT do, is assigning a "CopyOf" to the "asRecord" property, because that will create two copies, leaking one of them. That is what I was trying to point out in my original reply above. In other words, this line is WRONG, because it will result in a memory leak:

Best Regards,
Danijel Tkaclec

Ok, now I get it :)
I will use this fire-and-forget solution


Thanks a lot, Danijel!