For Mailet API v3, I'd like to add:
public InetAddress getRemoteAddress();
Both getRemoteHost() and getRemoteAddr() can be implemented based upon an
InetAddress object, and when dealing with the IP address, having an
InetAddress is faster than having to convert from the String form.
This isn't a completely simple change because of compatibility with existing
stores, but not too difficult, either, since we properly have
readObject/writeObject methods, which give us the control we need to
marshall the format into/out of memory.
Now ... is it worth it? Good question. Right now we only use
getRemoteAddr() in the DNSRBL and RemoteAddr matching. I've also got the
GeoMatcher code pending, which will use it. And the IP filtering
(short-circuiting in the handler) code will benefit from it.
Thoughts?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
