We should consider the field name. Revel was inspired from the Rails and Play web frameworks. We can also consider the naming in other popular web frameworks like Node.JS and PHP:

• request.ip and request.remote_ip Ruby on Rails
• request().remoteAddress() Java Play
• request.connection.remoteAddress Node.JS
• Request::$client_ip and @_SERVER['REMOTE_ADDR'] Kohana PHP

Does anyone have any preference? I feel there is value in choosing a naming convention that will be familiar to developers who have used other web frameworks.

I have read your inputs, below is equivalent to Go http.Request.RemoteAddr and it's language level-

• request().remoteAddress() Java Play
• request.connection.remoteAddress Node.JS
  @_SERVER['REMOTE_ADDR'] Kohana PHP

Below one, customized by respective framework-

• request.ip and request.remote_ip Ruby on Rails
• Request::$client_ip Kohana PHP

Now, let's come to Revel. It can provide -

• ServerIP - comes from app.conf - http.addr or local loopback address
  • Or We call this as IP and add documentation explaining this is server ip. Like Ruby SO question
• ClientIP or RemoteIP in the Controller
  • Both terms is known in the industry and developers familiar to it

@brendensoares what is the final take on this?

Thanks for taking the time to consider our options on this. Let's merge this!

PS - what can we do to document this new API addition?

ClientIP method already has godoc, all we need to do is updating controller attributes in the manual.