finn.no last thursday came out with an upgrade to tiles-3. I had applied the code when testing tiles-3 in the sandbox before the merge to trunk. Since then it's undergone testing and profiling so we've built enough confidence to bring now a recent tiles-3 build out into production.
For us the primary motivation was the OptionsRenderer and the PublisherRenderer. The former making out tiles xml files _alot_ easier to read and work with. Performance looks great too. I was a little worried about TILES-522 (we had patched tiles-2 to address it but now we're using a vanilla tiles-3 build). We are pushing up to 200 requests/second/jvm through the tiles-3 framework. It's hard to say for sure but it looks like tiles-3 has given us a ~5% speed improvement. Any possible theories to this? This puts us in a position where we'd like to push towards a beta release of tiles-3. Nicolas: have you more things than the tiles-request-api changes for the "3.0 horizon"? ~mck -- "We are what we think. All that we are arises with our thoughts. With our thoughts, we make the world." Buddha | http://tech.finn.no | http://github.com/finn-no |
signature.asc
Description: This is a digitally signed message part
