Mike Fechner and Peter Judge like this.
  • Peter Judge (Consultingwerk)

    How long is a piece of string? :D

     

    I don't think that there's any issue with lots of endpoints served by PASOE per se. But there are a lot of "it depends" with respect to how those are served - using web handlers vs. the REST tooling (ie PAAR files); how specialised vs general purpose the ABL code behnd those endpoints is; etc.

     

    If you're talking OE REST - that is PAAR files - then you can potentially run into development bottlenecks if multiple developers need to work on (create, modify) those endpoints and their definitions.

  • Jorge Olguin (super carnicerias hernandez sa de cv)

    Thanks!!! Great insight

     

    And yet.... lots of endpoints served by PASOE per se., is somewhere around 100, or as far as 10,000?

     

    (currently running 75, paar based, one developer)

  • Jorge Olguin (super carnicerias hernandez sa de cv)

    One thing I mus have added, is the nightmare to find the endpoint in the "Rest Resource URI Editor" listing. As they are not alphabetically ordered.. I wonder how are the ordered, it is not by endpoint name, nor by date created, neither by sourcing class to the endpoint...