Exploring Remoting...

Yuri Maggi wrote:

> In this case, how to correctly match callback messages to the right thread ?
> I am really a newbie on this matter and any will appreciate any help.
> Thanks...

I'm not sure what you mean with that.

If you have a class, deriving from TInterfacedObject or TnxInterfacedObject
that implements that callback interface, you can create multiple instances of
that class for your different contexts.

[yuri.maggi]

I think I´ve some clues and will try them in some tests. Anyway, it should be very nice having more examples on the two-way remoting. As long as I see, this is a very powerful engine and we do not see too much discussions on it. Thanks...

Thorsten,

One more question: in this multi-thread concept, do I have to care about
releasing the remoting instances just created ?

Thanks.


"Thorsten Engler [NDA]" <thorsten.engler@nexusdb.com> escreveu na mensagem
news:xn0himrdu2svtt5000@news.nexusdb.com...
> Yuri Maggi wrote:
>
>> In this case, how to correctly match callback messages to the right
>> thread ?
>> I am really a newbie on this matter and any will appreciate any help.
>> Thanks...
>
> I'm not sure what you mean with that.
>
> If you have a class, deriving from TInterfacedObject or
> TnxInterfacedObject
> that implements that callback interface, you can create multiple instances
> of
> that class for your different contexts.

Yuri Maggi wrote:

> Thorsten,
>
> One more question: in this multi-thread concept, do I have to care about
> releasing the remoting instances just created ?

I'm not quite sure I understand your question. Normal interface semantics,
including reference counting, are in effect.

If you haven't done so before, you might want to read the blog posts I made
about remoting in the past:

http://www.nexusdb.com/support/index...f-fundamentals
http://www.nexusdb.com/support/index...=intf-advanced
http://www.nexusdb.com/support/index...tf-aggregation
http://www.nexusdb.com/support/index...ng-big-picture
http://www.nexusdb.com/support/index...-example-basic

I´ve already read all posts and a lot of other stuff... A little bit hard to
understand everything well in the short time.

Maybe, if possible, you could check the code I´ve sent on the binaries that
implements an interface to transfer streams using as basis the one-way
remoting example. The thing is that is very clear when the instance is
created but it is not clear to me when the instance is released. I´d
appreciate any advice...



"Yuri Maggi" <yuri.maggi@engilab.com.br> escreveu na mensagem
news:4e67e399$1@DSVR011613....
> Thorsten,
>
> One more question: in this multi-thread concept, do I have to care about
> releasing the remoting instances just created ?
>
> Thanks.
>
>
> "Thorsten Engler [NDA]" <thorsten.engler@nexusdb.com> escreveu na mensagem
> news:xn0himrdu2svtt5000@news.nexusdb.com...
>> Yuri Maggi wrote:
>>
>>> In this case, how to correctly match callback messages to the right
>>> thread ?
>>> I am really a newbie on this matter and any will appreciate any help.
>>> Thanks...
>>
>> I'm not sure what you mean with that.
>>
>> If you have a class, deriving from TInterfacedObject or
>> TnxInterfacedObject
>> that implements that callback interface, you can create multiple
>> instances of
>> that class for your different contexts.
>

Yuri Maggi wrote:

> I´ve already read all posts and a lot of other stuff... A little bit hard to
> understand everything well in the short time.
>
> Maybe, if possible, you could check the code I´ve sent on the binaries that
> implements an interface to transfer streams using as basis the one-way
> remoting example. The thing is that is very clear when the instance is
> created but it is not clear to me when the instance is released. I´d
> appreciate any advice...

As with any interface, the instance is released when the last interface
reference to it goes out of scope.