Skip to content

History / API_QS

Edit page New page

Revisions

  • Updated API_QS (markdown)

    @davidpodeur davidpodeur committed Mar 16, 2020
    b2bb251

  • Updated API_QS (markdown)

    @davidpodeur davidpodeur committed Mar 16, 2020
    c424b56

  • Updated API_QS (markdown)

    @davidpodeur davidpodeur committed Mar 16, 2020
    4cebfc7

  • unify concepts and access between the two APIs

    @mpup371 mpup371 committed May 9, 2019
    8df73e9

  • use the "PUT3 verb to push message without body

    @mpup371 mpup371 committed May 3, 2019
    5decc26

  • Don't make difference between blobs and elements, the way they are stored is decided by the server, not by the user. So probably an element should always contain a reference to a blob, even if it's stored in memory.

    @mpup371 mpup371 committed May 3, 2019
    f2ab7bc

  • first draft for messages associated with Blobs, which are different from elements containing data, but have similar API.

    @mpup371 mpup371 committed May 3, 2019
    d390e31

  • Updated API_QS (markdown)

    @mpup371 mpup371 committed May 3, 2019
    6048f88

  • Updated API_QS (markdown)

    @thefab thefab committed Jan 9, 2019
    9bdd099

  • Updated API_QS (markdown)

    @thefab thefab committed Jan 9, 2019
    a26f470

  • Updated API_QS (markdown)

    @thefab thefab committed Dec 21, 2018
    6fae073

  • Updated API_QS (markdown)

    @thefab thefab committed Dec 21, 2018
    d46c7fb

  • Updated API_QS (markdown)

    @thefab thefab committed Dec 21, 2018
    f74088f

  • Updated API_QS (markdown)

    @thefab thefab committed Dec 21, 2018
    a19a230

  • Initial Home page

    @thefab thefab committed Dec 21, 2018
    2caa94b