How do you maintain the old API when it comes time for updates?

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #48327
    jiyite
    Participant

    Here’s the problem: we have an old API that seems to work, but is no longer up to date. I’m starting to wonder how we can support such a thing when new versions start coming out one after another. I don’t want clients to have to go through the trouble of switching to a new version, but leaving things as they are is not an option either. Maybe someone has experienced how to smoothly migrate users to the new API version so that no problems arise and you don’t have to torn between supporting the old and implementing the new? What approaches really work?

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.