[Tile-serving] New option for tile server: Nginx+Tirex: TileMan
Hiroshi Miura(@osmf)
miurahr at osmf.jp
Sun Jun 2 03:39:28 UTC 2013
Hi there,
On 05/24/2013 01:13, Frederik Ramm wrote:
>
> On 05/23/2013 05:53 PM, Kai Krueger wrote:
>> What's the advantage of talking to tirex directly, compared to using the
>> mod-tile socket emulation? What should mod_tile be able to do, that it
>> currently can't with the emulation layer?
>
> One thing I always wanted to have is better control over render priorities - i.e. having more than the 4 or 5 hard-coded priority values in renderd. Apart from that, the Tirex protocol allows not only the enqueuing but also the dequeuing of tiles (e.g. if the module decides that it takes too long to render), and more precise return messages.
>
> I also find UDP (which Tirex uses) a more elegant solution than using a streaming socket for what *is* essentially a datagram protocol but I guess that's a design choice.
IMHO, from my development experience of Tirex protocol, I can say that
a choice of unix domain datagram and priorities, queue/dequeue is theoretically as same as
message queue features such as priority queue, publish/subscribe, asynchronous coupling.
Tirex seems be designed on message queue ideas.
I'm also interested in scale-out configuration of tile servers like as following diagrams.
https://dl.dropboxusercontent.com/u/90779460/extensive_configuration.png
I believe Nginx, TileMan and Tirex combination realize a larger Tirex clustering configuration.
TileMan: https://osmfj.github.io/tileman
--
Hiroshi
More information about the Tile-serving
mailing list