-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/10/12 12:06 PM, Paul Lindner wrote: > Look at the usage of CompletionService in shindig to see how this > is useful. > > Sure you *could* wrap every API call in a Callable, however that > would lead to extra thread consumption. > > Another benefit of a Future<..> api is that you can execute a small > amount of code on the request thread to set up your Future. This > allows for ThreadLocal use on the servlet thread, request scoped > guice injection, and more. > > I agree that it's a bit ugly, and you can get if you need to take > the output of a Future and pass it to the input of another it gets > confusing (even with Futures.transform(...) from guava) >
I'm not sure we're on the same track here. I do not oppose against the use of Future, but question its use in the SPI-parts of Shindig, like PersonService. - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQIcBAEBAgAGBQJQdVujAAoJEKF/mP2eHDc4KwcP/21/2Dn2iUrCZNu5n45PPNZX LbzyhQOxQNjMr+nbrjRG/V6itM01GEFA8h2uEo0BmxbbbEogP6SUvxSJ8At2AA59 Nf4sYGY+ImX1LjFRz216/s32EWiWjeSTJ61JEygFQt78iT8M27lAZt1cwDCz4m5U WgjCOSrj9VMFitQj75suwjeMvaI39wxiOje4O5Ud2GfAeO7dXYn0sZqEeCF4ddMU aFDhei8m7aHO8M9gQ6tmPyv0PgUuG1u4YsbxNZKaOCErL8vFNv8fofKEgKm1zTFp A41TlWJM0dxhrKiWGwpMB3mpwT2gAAPeJJluuyeWfB0CzAchelZs4/Z03I5v7cZS z1av8VmQO/SWOjtowuRw++j7qpoYyozScLzuMj1kTsA++UEIt1j1vkb93YXdicBh YoC/7JtGf9MFgdhEOg/AtxOyC71HwabjhoEoB7cp9ZKpcEpvvj1Pjv42s7XtgzO/ QiWyS4rbPFeymuykk2xay4T1DGqSJsW+XjqjLe7YqsqnB7i3DMtdwwR8gA7ZdZLs ePCULEX5QCbzdzmtPEfN/Y+dGY8awjKoR90+6S6QMexuBQOWo96a7qLsgTpW1VI8 JzKE5xB1mh1Ip9qsvlYk58x0ib7KLV4CgyMuuC1XmeNJRntVYuRsH8NAbCJyhRyk P7HAYcUVjHq5Lvq8iT8h =miJf -----END PGP SIGNATURE-----
