#1 2013-12-01 13:19:39

nirnir
Member
Registered: 2013-11-11
Posts: 66

ICopiable interface

I can't find that http://synopse.info/fossil/info/f23a869a36
on the last build,  why ?

Offline

#2 2013-12-01 15:15:58

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,182
Website

Re: ICopiable interface

This was indeed a wrong good idea.
I wrote this late in the night, just after having read http://www.deltics.co.nz/blog/posts/2177 and passing the last previous days in the middle of Java frameworks...

There was no need of using an interface, when all we expected to find was to make TSQLRecord.CreateCopy() method virtual.

It was not proper interface use, but interface ab-use.
smile

Interfaces have a cost when creating an object.
So I reverted the change to another easier pattern: declare TSQLRecord.CreateCopy() as virtual, therefore allow custom copy of any TSQLRecord.

Offline

#3 2013-12-01 16:11:58

nirnir
Member
Registered: 2013-11-11
Posts: 66

Re: ICopiable interface

Ok ,thanks,
If we are already talking about interface , how do I register a service  to be used only on the server side and not exposed to the client ?

aServer.ServiceRegister(Trt_mangr,[TypeInfo(IrtMng_1)],sicShared);
aServer.ServiceRegister(Trt_mangr,[TypeInfo(IrtMng_2)],sicShared);


IrtMng_1,IrtMng_2 are interfaces to the same Trt_mangr object

IrtMng_1 is used from the client
IrtMng_2 should be used from other units on the server only

Offline

#4 2013-12-01 22:23:12

ab
Administrator
From: France
Registered: 2010-06-21
Posts: 14,182
Website

Re: ICopiable interface

You can change the service rights, and use DenyAll() method.

Offline

Board footer

Powered by FluxBB