On Feb 13, 2009, at 5:19 PM, Ryan Lane wrote: > I think I also like #2. I'd imagine this could also work for dynamic > page list or semantic mediawiki queries... Both of which I'm > interested in. > > Should this be a GET, or a POST? The graphviz extension can take > arbitrarily long content between the opening and closing tags, and > would likely be too long for a GET request.
It needs to be a GET request and these are limited to 50K in the client library we are using (could probably be patched) and 15K in MW/ PHP/or the Webserver (didn't check who generated the 413 response). > > I'm thinking I could make a special page that takes the content, and > attributes, and returns the location of the image. Should I be posting > and returning XML? API-like work is fairly new to me. I assume that your extension (did not find a working demo) uses some hashing to store and reference generated images. If this is the case you could use this hash to identify these images for the PDFs. Heiko --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mwlib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mwlib?hl=en -~----------~----~----~----~------~----~------~--~---
