You are not logged in.

Which DCOP interfaces /mechanism do you use?

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

zztop

Beginner

  • "zztop" started this thread

Posts: 7

  • Send private message

1

Monday, June 13th 2005, 10:36am

Which DCOP interfaces /mechanism do you use?

Which DCOP interface/mechanism do you use in your projects?

No votes have been recorded yet

0%

pure asynchronous 'send' (for request and answer)

0%

synchronous 'call'

0%

asynchronous 'callAsyn'

0%

Whut ?!?

I know, most of you will say: depends on what I want to achieve with DCOP...
My question is mainly about whether the callAsync interface is used at all.
I suppose on server/service side to the transactions help to make the server stay reactive and respond even if a request is currently running. But who uses DCOPClient::callAsync on client side?
In most cases DCOP is only used to notify somebody about something (send) or poll some status information. But what if I want the server to do something for me (which may take some time) and then report to me. I could block on the answer (call), wait for an async event, e.g. the server responds with another (send), or I could make a callAsync which would save me the effort to handle a state machine for simultanous replies.

So which mechanism do you actively use in your projects?
There's no place like ::1