Hi,
I like the idea of JSON and the shortening too.
A combination of both should do i guess. And probably the RPC service could be
one which does not need authentication like the database listing webservice.
Thanks,
Sharoon Thomas
On 27 Aug 2010, at 11:40, Tobias Paepke wrote:
> On 27.08.2010 12:26, Cédric Krier wrote:
>> On 25/08/10 23:02 +0200, Cédric Krier wrote:
>>> On 25/08/10 16:08 -0400, Phillip Heller wrote:
>>>>> I think we should think about more powerfull URI scheme (perhaps
>>>>> REST-like) to
>>>>> be able to get domain/context inside. The best should be to be able to
>>>>> encode
>>>>> any of the ir.action.
>>>> Can you give some examples of how you might encode context variables or
>>>> invoke other actions?
>>> No I don't have.
>> Perhaps simple use parameters with value encoded in JSON.
>>
>> like tryton://..../party.party?domain=[['name', '=',
>> 'Bob']];context={'language': 'en_US'}
>>
> I like the idea of JSON
>
> if used in for example in emails it would lead to a really long and ugly url
> which could break on end of line.
>
> what about kind of shortening service inside tryton? like:
> tryton://.../Voh7eel6hoa3coo8faehahgoh5uijoh3
>
> an rpc call could generate it for external services.
>
> maybe we could pack that whole stuff into a base64 encoded string.
> but nevertheless there exists a maximum length of urls in several browsers,
> maybe mail clients, too.
>
> I don't know if its a problem if external handlers would be triggered like in
> this case.
>
> just my 2c
>
> tobias
>
> --
> [email protected] mailing list
--
[email protected] mailing list
