Issue 773:  Current.timeout part of service context? (transactions)
Source:  (, )
Nature:  Uncategorized Issue
Severity:  Minor
Summary: Summary: Is the Current.timeout part of the service context? If not, how does one set the timeout on subtransactions? If so, how does the server retrieve this information (Current::get_timeout() doesn"t exist).

Resolution: 
Revised Text: 
Actions taken:
October 14, 1997: received issue
Discussion: 

End of Annotations:=====
Return-Path: <nagler_robert@tandem.com>
Date: Tue, 14 Oct 1997 09:16:38 -0700
From: Rob Nagler <nagler_robert@tandem.com>
To: transactions@omg.org
Subject: Question about CosTransactions behaviour

I am implementing CosTransactions v1.1 as described in orbos/97-03-04.
I have a few questions.  I apologize in advance if this isn't the
correct mailing list for such issues.


3) Minor point: Is the Current.timeout part of the service context?
If not, how does one set the timeout on substransactions?  (Ignoring
the fact I'm not supporting them... ;-)  If so, how does the server
retrieve this information (Current::get_timeout() doesn't exist).

Thanks in advance,
Rob