Well... there was a open case about this, which is now closed... https://issues.apache.org/jira/browse/FTPSERVER-223
Are you sure this is still an issue? On Fri, Mar 18, 2011 at 7:46 AM, Christian Gosch <[email protected]> wrote: > Hi, > > I just looked at the implementation of > DefaultFtpletContainer.onConnect() and saw that it processes all > contained (registered) Ftplets by traversing the (concurrent hash) map > of declared Ftplets, just as onDisconnect(). > > But it does so based on the ftplets.entrySet() and the sort order which > it imposes on the entry set, which in turn is "undefined" in that it > does not guarantee any special sort order. > > Why is the concurrent map ftplets not implemented as a map with a > reliable sort order depending on the key values? > > It may be good practice to have every registered Ftplet act > independently of any other in the same container, but there may be good > reasons to have an ordered sequence, may be by order of declaration, or > by order of key or whatever may be appropriate. > > Is there a special rationale behind this? > > > btw: I did not yet find any time to play around with this really :-( > > > Regards, > -- > Dipl.-Inform. Christian Gosch, PMI PMP > Systems Architecture, Project Management > > inovex GmbH > Büro Pforzheim > Karlsruher Strasse 71 > D-75179 Pforzheim > Tel: +49 (0)7231 3191-85 > Fax: +49 (0)7231 3191-91 > [email protected] > www.inovex.de > > Sitz der Gesellschaft: Pforzheim > AG Mannheim, HRB 502126 > Geschäftsführer: Stephan Müller > > > >
