Johan Sundström wrote:
> On 3/13/07, Johan Sundström <[EMAIL PROTECTED]> wrote:
>   
>>> [...] &mime-type=output-mime-type [...]
>>>
>>> [...]
>>>
>>> output-mime-type can be anything you want. It is entirely optional.
>>>       
>> That doesn't quite seem to work; misdocumented? I fail to override the
>> application/json(p) output of writers exhibit-json(p):
>>     
>
> I later found out it was just misdocumented (should read "mimetype").
> I fixed the wiki docs.
>
> I would still like upstreams help to cater the JSONP &callback=
> argument, though.
>   
The reason for out-callback is because I would like the architecture to 
support custom parameters for both readers and writers. Readers' 
parameters start with in- and writers' with out-. Do you think it's 
worth breaking this pattern? At the moment, there's no other parameter 
being supported by any other reader or writer.

David


_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general

Reply via email to