Aucun résultat
Il n'y a pas d'objets correspondant à votre recherche... Vérifiez que l'orthographe des mots est correcte ou élargissez votre recherche pour obtenir des résultats !
My delcampe store is linked to my website via the API. I'm noticing that the products put on sale last week are coming up very slowly (currently, every night, my products put on sale from Delcampe on 31/10 are coming to my website, in small numbers).
Is this problem already known?
when you send a new item using the API, your call is registered but is not handled immediately if the images have to be downloaded from a remote server.
In this scenario your new sell is held in a queue that is basically managed first-in, first-out.
Depending on the load on this queue the download can happen quite immediately or take sometimes hours. The SLA is 24 hours max.
Only when the download is complete, you'll receive the notification with the new ID.
when you send a new item using the API, your call is registered but is not handled immediately if the images have to be downloaded from a remote server.
In this scenario your new sell is held in a queue that is basically managed first-in, first-out.
Depending on the load on this queue the download can happen quite immediately or take sometimes hours. The SLA is 24 hours max.
Only when the download is complete, you'll receive the notification with the new ID.
Hi Laurent
I know the flow but the problem is for every item listed I need two calls:
one for list the item
one (or more) for retrieve item id on your site
Obviously I don't want to teach you but as other services the best scenario is to show the id immediatly after your system receive the list call and show the item on item list at your convenience
Sometimes my system need 4/5 calls before retrieve the item id. At the end of the day for your system means tons of call for nothing
the first implementation of this API endpoint was real time, as you would still like it to be, if I understand well your request.
However this lead to many problems, because we usually hit the maximum allowed quota on the remote server (well the other side also have to protect its infrastructure, especially on low cost providers) and in the end our IP/infrastructure is blacklisted or is voluntary responded slowly.
Then from your perspective, the API call will appear hung, will timeout, not knowing whether the sell is created or not, and you could have duplicates by retrying.
That's the reason why we now use a queue for new sales. When it is is empty, your call will be treated within seconds, but not within the call itself.
Like in every systems, people tends to do the same thing at the same time, and sometimes you have to wait in the line.
Increasing infrastructure resources is not always a solution, if we hit too hard on remote servers we could be reported as attackers, and banned endlessly, sometimes across multiple organizations (it has happened).
You have to call multiple times to retrieve the final ID of the sale. This call is, by far, lighter (hundreds of magnitude) than the one which process the images of a new sell.
Ce sujet datant de plus de 6 mois, il n'est plus possible d'y répondre.
Paramètres des cookies
Information concernant les cookies
Notre site utilise des cookies pour les finalités suivantes : vous fournir les services demandés, assurer la sécurité sur notre plateforme, garder en mémoire vos préférences afin de rendre votre navigation plus agréable, réaliser des statistiques dans le but d’adapter notre site à vos besoins, afficher des vidéos et vous permettre de partager du contenu sur les réseaux sociaux.
Certains de ces cookies sont nécessaires au fonctionnement de notre site, d’autres peuvent être paramétrés selon vos préférences.
En savoir plus