I figured as much but wanted to see if there was anything else I could
suggest based on a possibly expanded description. Am just trying to help -
but again, do not have much expertise in netty. Somehow your web layer
needs to be able to communicate/manage/reference/whatever your business
layer (o
Hi Sean,
Our business is monitoring end-user systems. So an IP address of that
remote system *is* part of our business logic ;-) I don't know why I'd
have to justify it, just look at HttpServletRequest, you can get the remote
address of the connected entity using that API, but because we're in n
Craig,
It doesn't seem like netty channels ought to be getting passed around your
business layer, since they're a fairly low-level concept. Traditionally
your business objects would be brokered and manipulated by some kind of
service or data access layer that would know about transport concerns...
Hi Sean,
Thanks for the response! First, is the netty Channel available in some
layer that I can access and pass up to our business logic layer?
Preferably without changes to RestEasy, but we can probably take on that
work if we were sure the functionality would be accepted into RestEasy.
Second,
I'm not an expert in Netty - and I hope I understood your question - but
It looks like there's a "remoteAddress()" on Channel (name different in
netty 4 vs. 3).
http://netty.io/4.0/api/io/netty/channel/Channel.html#remoteAddress()
Note that this can deceive if there's a gateway / proxy in pl
Hi all,
I'm wondering if there's a way to get the remote client's hostname/ip
address when we're using Netty. Normally we'd just use @Context
HttpServletRequest and getRemoteAddr() method, but we're in Netty and don't
have that available to us.
Is there any way we could do this? Possibly writin
