Subject | Re: [Firebird-Architect] Fetching from a non-cursor |
---|---|
Author | Jim Starkey |
Post date | 2010-10-18T13:46:48Z |
On 10/18/2010 3:34 AM, Alex Peshkoff wrote:
people that immutable means immutable when it comes to interfaces. The
ability to add new interfaces leaving the old intact is a very powerful
feature. It also gives you complete freedom to decide what is client
side and what is serve side and giving you the freedom to change your mind.
Two pieces of advice, though. Make it COM, not almost COM or like COM
or virtually COM. Second, don't bother the DCOM -- do your own
networking and marshalling.
> On 10/15/10 23:50, Jim Starkey wrote:COM is probably a sound foundation, though you will have to convince
>>
>> The main point, however, is never, ever build a static structure into an
>> API. The structure will always need extending for some unanticipated
>> reason, and a change will break upwards compatibility.
>>
> I've used COM-like objects in firebird3.
>
>
people that immutable means immutable when it comes to interfaces. The
ability to add new interfaces leaving the old intact is a very powerful
feature. It also gives you complete freedom to decide what is client
side and what is serve side and giving you the freedom to change your mind.
Two pieces of advice, though. Make it COM, not almost COM or like COM
or virtually COM. Second, don't bother the DCOM -- do your own
networking and marshalling.