[Tilesathome] either nodata or Forked render failure
Sebastian Spaeth
Sebastian at SSpaeth.de
Tue Aug 26 21:51:24 BST 2008
Florian Lohoff wrote:
> Hi,
> it seems somethings still essentially broken - Currently all requests
> either produce a NoData or a Forked render failure - It seems there are no
> requests successfully processed ...
I have just committed my final commit and things work fine for me now:
(r10189). I have added code to immediately request the data in stripes
if we know that the tileset is going to be complex. The API was just
failing on complex requests, this is nothing that is new in the client
and was cause by the client.
I have disabled the inscape forking for now completely until I have
audited that code. Forking is still possible for orp'ing and
beziercurv'ing and works well for me.
I have upped the latest client version to this version now and would be
interested in error feedback.
if you get orp failures please make sure that orp is also at its latest
svn version.
Thanks for bearing with this. I feel we are getting on solid ground
again. The next major works will be done in a private SVN branch and
merged into HEAD only when it is deemed stable by a few people.
spaetz
More information about the Tilesathome
mailing list