thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Slee" <ms...@facebook.com>
Subject RE: Tracing request origin?
Date Thu, 07 Aug 2008 18:45:06 GMT
Sorry if this has already been replied to (didn't see one).

This isn't possible in the application layer, because there's no
requirement that requests to a service handler have to be made via a
network at all, hence IP might be irrelevant. This is encapsulated
entirely at the transport layer.

If you need to trace this, you can either modify/extend a TServer or
TServerTransport of your choice to keep track of this information in
whatever means you find appropriate, or you can pass along client
information as part of the actual method call.

If your application depends on client information to function properly,
then I'd recommend the latter as it really is part of the application,
but if this is just for debugging, then I'd probably recommend the
former.


-----Original Message-----
From: Phillip B Oldham [mailto:phillip.oldham@gmail.com] 
Sent: Wednesday, July 30, 2008 2:13 PM
To: thrift-user@incubator.apache.org
Subject: Tracing request origin?

Is it possible running a thrift server to see what IP the request
originated from?

--
Phillip B Oldham
phillip.oldham@gmail.com
+44 (0) 7525 01 09 01

Mime
View raw message