Amos, It seems these sorts of problems will naturally happen when all changes in a (good-sized) project HAVE to go through ONE person, and that person has other full-time commitments like job(s) and family... In addition, there are always timing and communications issues...
I too have brought (serious and complicated) things up that never went anywhere (though I really tried to "make the case"), including one set of problems that affects the entire library (and which I know I'll have to get back to; one client is getting a security audit, and the auditors are reviewing the error handling of all custom code). My hope was that enough other users would be interested in certain problems that we could gather in groups of interest, work on the problems (perhaps with some small guidance from Lukas), and once a reasonable solution was arrived at and implemented, Lukas could review and commit it. I was interested in your problems, but have very little experience with Synapse and emailing, (don't remember now what the network issue was), and don't have enough time to get my own work done! After more work and investigation, I *will* return to the "core" problem I think the lib has. If you still have issues, I suggest you bring them up again as they become important. I, for one, will definitely take a look, but I don't know how much I can contribute... ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
