• synchronet web api

    From Tracker1@VERT/TRN to echicken on Thursday, February 04, 2021 05:58:24
    echicken,

    Any interest in coordinating/collaborating on this?

    I'm starting API interfaces for an spa focused web ui. Are there any libraries/modules you would suggest I look at for some of this based on
    what you've done, I know some parts of webv4 are using APIs, and a lot
    is just inline. I'd prefer to keep what I'm doing as compatible as
    reasonable with what you've done so far, specifically session/auth and
    the modopts.ini in particular.

    Planning on having the api endpoints effectively be /sapi/*.ssjs in a
    separate directory, so as not to conflict with what you're working on,
    but wouldn't mind having it useful to both. I'm planning on starting
    with the newuser options, and user creation api first. Not sure about integrating some similar behaviors to the first user creation via the bbs/terminal interface.

    (note: replied on a webv4 message so the "to" would be set via nntp)
    --
    Michael J. Ryan (tracker1)
    +o roughneckbbs.com

    ---
    þ Synchronet þ Roughneck BBS - roughneckbbs.com
  • From echicken@VERT/ECBBS to Tracker1 on Thursday, February 04, 2021 14:53:53
    Re: synchronet web api
    By: Tracker1 to echicken on Thu Feb 04 2021 05:58:24

    I'm starting API interfaces for an spa focused web ui. Are there any libraries/modules you would suggest I look at for some of this based on

    Anything useful and reusable would be in webv4/lib/, which is a lot of stuff. Most inline server-side code is very much tied to the view and won't be useful. If it belongs in a library I usually put it in one unless I'm being very lazy.

    is just inline. I'd prefer to keep what I'm doing as compatible as reasonable with what you've done so far, specifically session/auth and the modopts.ini in particular.

    Some of the settings in modopts.ini may be useful and interchangeable. The session store is pretty simple and is just an ini file under data/user/#.web.

    Authentication is not well implemented in webv4 and I plan on replacing it soon. I would not pursue compatibility with that at the moment.

    I wouldn't worry too much about compatibility unless you plan on integrating with webv4 somehow. Although I will maintain, enhance, and support webv4 indefinitely, I don't see any big changes or new features coming anytime soon. I have another project underway which is similar to yours but probably has a few different goals - and I'm not giving much thought to webv4 compatibility when I work on it.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com