Home | TMF: Stats & Records | TM2: Stats & Records | Forum | Login |
Dedimania forum
Feel free to express yourself on your favorite dedicated related tool.
You are not logged in.
Pages: 1
- Index
- » Scripts using Dedimania
- » a new controller script for tmuf dedimania should use the old api ?
#1 2024-01-02 14:28:47
- Petri (-:|>*
- tm2:reaby
- New member
- From: Finland
- Registered: 2014-12-16
- Posts: 3
a new controller script for tmuf dedimania should use the old api ?
Hi Slig and Xymph,
I'm about to develop a new dediamania client (for MINIcontrol)
I'm uncertaint shuold i use the old or the new api for tmuf/tmnf calls.
Also it seems the old api has obsolete most of the methods, what should i use ?
Thanks,
Reaby
Offline
#2 2024-01-02 19:06:49
- Petri (-:|>*
- tm2:reaby
- New member
- From: Finland
- Registered: 2014-12-16
- Posts: 3
Re: a new controller script for tmuf dedimania should use the old api ?
Idk why, but the authentication fails after few minutes of server being idle...like when i do new fetch for records.
Also there is faultcode which should be int, but it's empty... and nodejs xmlrpc deserializer doesn't like that at all,
patched it locally with:
const data = (await response.text()).replaceAll("<int></int>", "<int>-1</int>");
Offline
Pages: 1
- Index
- » Scripts using Dedimania
- » a new controller script for tmuf dedimania should use the old api ?