- From: Alexandre Bourlier <alexandre@happy-dev.fr>
- Date: Tue, 2 Apr 2019 17:53:28 +0200
- To: Dmitri Zagidulin <dzagidulin@gmail.com>
- Cc: Alexandre Bourlier <alexandre@happy-dev.fr>, Benjamin Goering <ben@bengo.co>, Mitzi László <mitzil@inrupt.com>, public-solid <public-solid@w3.org>
- Message-ID: <CAHrPJy+2Bp6ppaYBatVeBE=rmA8GepNXAd-wyiGmEuZtg_-kWg@mail.gmail.com>
Fair point. I thought the opposite but I am totally fine with it. Will write down an issue ASAP. On Tue, 2 Apr 2019 at 17:49, Dmitri Zagidulin <dzagidulin@gmail.com> wrote: > > I'd like to quickly discuss that before formalizing the problem on Github > > Got it, that makes sense. I think what Ben (and myself) are trying to > express is that the priority is the other way around. Raising Github issues > == cheap, talking during the call == expensive. > > On Tue, Apr 2, 2019 at 11:47 AM Alexandre Bourlier <alexandre@happy-dev.fr> > wrote: > >> I fully support that process also. >> >> I would first like to present my case orally this time to understand if >> the problem is relevant to the community or specific to our router and the >> way we handle resources. >> >> But I agree with the process of creating an issue. I am just not so sure >> if it is an issue you guys will also face. I'd like to quickly discuss that >> before formalizing the problem on Github >> >> On Tue, 2 Apr 2019 at 16:46, Dmitri Zagidulin <dzagidulin@gmail.com> >> wrote: >> >>> +1 to Ben's concerns -- I think we should encourage users of first >>> bringing up issues like that in Github, and only using scarce phone call >>> time on high-bandwidth items. >>> >>> On Tue, Apr 2, 2019 at 10:42 AM Benjamin Goering <ben@bengo.co> wrote: >>> >>>> Alexandre, is their an existing issue to reflect your concern with >>>> those URLs? i.e. has anyone had a chance to help asynchronously before we >>>> try to deal with it synchronously? >>>> >>>> On Tue, Apr 2, 2019 at 10:11 AM Alexandre Bourlier < >>>> alexandre@happy-dev.fr> wrote: >>>> >>>>> Hi Mitzi, >>>>> >>>>> I would like to add : nasty id encoding in URLs. >>>>> Example : >>>>> http://127.0.0.1:8000/act/action-group-detail/@http%3A%2F%2F127.0.0.1%3A8000%2Fapi%2Faction-groups%2F1%2F >>>>> <http://127.0.0.1:8000/act/action-group-detail/@http%3A%2F%2F127.0.0..1%3A8000%2Fapi%2Faction-groups%2F1%2F> >>>>> >>>>> We are providing a terrible experience to our users by having to >>>>> encode the ids in the urls. >>>>> The community might have a solution for this. >>>>> >>>>> See you soon ! >>>>> >>>>> On Mon, 1 Apr 2019 at 13:55, Mitzi László <mitzil@inrupt.com> wrote: >>>>> >>>>>> Hi W3C Solid Community Group, >>>>>> >>>>>> You can find the draft agenda and call in details of this weeks call >>>>>> at 14h CET on Thursday 4th April. [1] >>>>>> >>>>>> If you would like to add any items to the agenda please let me know. >>>>>> >>>>>> Mitzi >>>>>> >>>>>> [1] https://www.w3.org/community/solid/wiki/Meetings#20190404_1400CET >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> >>>>> Alexandre BOURLIER >>>>> 06 51 71 08 21 >>>>> http://happy-dev.fr >>>>> >>>> >> >> -- >> >> Alexandre BOURLIER >> 06 51 71 08 21 >> http://happy-dev.fr >> > -- Alexandre BOURLIER 06 51 71 08 21 http://happy-dev.fr
Received on Tuesday, 2 April 2019 15:54:03 UTC