[
https://issues.apache.org/jira/browse/FTPSERVER-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-252.
---------------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1)
1.0.0-RC1
Assignee: Niklas Gustavsson
I don't think we got a chance of doing something better than a UUID, so that's
what I added in rev 729782. It's available from FtpSession.getSessionId() as
well as in the MDC based logging (using the token "session").
> Maintain a session ID for every client session and make it available via an
> API call
> ------------------------------------------------------------------------------------
>
> Key: FTPSERVER-252
> URL: https://issues.apache.org/jira/browse/FTPSERVER-252
> Project: FtpServer
> Issue Type: New Feature
> Components: Core, Ftplets
> Reporter: Sai Pullabhotla
> Assignee: Niklas Gustavsson
> Fix For: 1.0.0-RC1
>
>
> Add a new method to the FtpSession to return a unique session ID of a
> particular FTP session. It is important that these generated session IDs are
> unique for the entire life of an FTP server installation, i.e., a given
> install of the FTP server should never generate a duplicate session ID. If we
> want to think one more step ahead, it may not be a bad idea to even use UUIDs
> if we plan on running the server clusters for load balancing and fail over.
> More information about this can be found at -
> http://www.mail-archive.com/[email protected]/msg00512.html.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
