[reSIProcate] Stateless proxy support

[Dennis Dupont]

I have been looking at the stateless-proxy example and the SipStack use
of the 
stateless ctor parameter.  It doesn't seem to me that the stateless
parameter is 
even used by the ctor at all.  
 
So how does SipStack support a stateless proxy?  It seems to me that
there is 
*always* a transaction created.  But from 3261, 16.11:
 
"A stateless proxy does not have any notion of a transaction, or of
   the response context used to describe stateful proxy behavior.
   Instead, the stateless proxy takes messages, both requests and
   responses, directly from the transport layer (See section 18).  As a
   result, stateless proxies do not retransmit messages on their own."
 
and
 
"A stateless proxy determines where to forward the request as
         described for stateful proxies in Section 16.6 Item 10.  The
         request is sent directly to the transport layer instead of
         through a client transaction."
 
So how would I code a stateless proxy in order to bypass the transaction
layer?
 
 
Thanks,
 
Dennis Dupont
Intelemedia Communications, Inc.
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050804/e3b164c5/attachment.htm>