-
Notifications
You must be signed in to change notification settings - Fork 215
Optimize application retrival API wrt Numbers #2517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Orestis, There is one-to-many relationship between Applications and Numbers. Related to your option (2), since you need to be able to produce an
Wouldn't that work? |
@gvagenas , i think what you suggest would work great. I can create a design document for core team to review and let you know. Is this ok with you ? |
Sure go ahead @otsakir |
- Updated Application entity - Provided integration test - Some work on ApplicationDao layer Refers #2517
Also updated application.xml in all places in codebase Refers #2517
- Added entity, converter and updated related components - Added unit test for converter Refers #2517
Being able to produce application-centric listings that also include Incoming Number information is not easily done. One can retrieve application IDs when retrieving Numbers but when retrieving applications the bound Number SID is not part of the response. Even retrieving a number-by-application-id is not possible.
Here are some solutions i can think of:
These are just some thoughts. We probably need a design document here and some thining from the core team.
The text was updated successfully, but these errors were encountered: