[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mico-announce
Subject:    Re: [mico-devel] What to do if a client's call is left hanging?
From:       Karel Gardas <kgardas () objectsecurity ! com>
Date:       2006-11-30 17:39:59
Message-ID: Pine.LNX.4.63.0611301832210.3881 () silence ! gardas ! net
[Download RAW message or body]


Hi Alan,

I'm afraid you'll probably need something like request timeout
feature.  Unfortunately it is not presented in the current MICO
release.  Fortunately someone from the MICO community already
implemented it a while back for some older MICO so if you are
interested in the project of updating the patch for the current MICO
HEAD, then please let me know.

Cheers,
Karel

On Thu, 30 Nov 2006, Alan.Makin@selex-comms.com wrote:

> A question from a newbie.
> 
> I've been tasked with learning about CORBA, in particular MICO, and to
> understand some of the exceptions and error conditions that maybe
> encountered within the system we are currently developing.  I must add
> there is nobody within our organisation with any CORBA experience.
> 
> We have one situation that we are a little unsure of and do not have the
> knowledge in house to offer a solution.
> 
> The situation is the client has made a request over the CORBA interface to
> the server.  The server is now processing that request with the client
> waiting for the response.  In my example server code I enter an infinite
> while loop (while(1)) so leaving the client waiting for the response.
> 
> I'm trying to discover whether there is a method, within MICO, that will
> allow the client to know something has gone wrong on the server (this
> situation does not produce an exception), maybe where the client request
> times out.
> 
> I've looked into the event service, unfortunately, we do not have a lot of
> say on how the server side of our system will be implemented so this may
> not be an option open to us.
> 
> The book I've been using as reference, Advanced CORBA Programming For C++,
> mentions messaging and callback but I've been unable to find enough
> information to determine if this is the solution for me.
> 
> So if somebody on this list can provide me with the right information or
> some pointers for where to look next I'd be very grateful.
> 
> 
> Thanks in advance
> 
> 
> Alan.
> 
> 
> 
> ------------------------------------------------------------
> This email and any attached files contains company confidential information which \
> may be legally privileged. It is intended only for the person(s) or entity to which \
> it is addressed and solely for the purposes set forth therein.  If you are not the \
> intended recipient or have received this email in error please notify the sender by \
> return, delete it from your system and destroy any local copies.  It is strictly \
> forbidden to use the information in this email including any attachment or part \
> thereof including copying, disclosing, distributing, amending or using for any \
> other purpose. 
> In addition the sender excludes all liabilities (whether tortious or common law) \
> for damage or breach arising or related to this email including but not limited to \
> viruses and libel. 

--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com
_______________________________________________
Mico-devel mailing list
Mico-devel@mico.org
http://www.mico.org/mailman/listinfo/mico-devel


[prev in list] [next in list] [prev in thread] [next in thread]