Architecture Question (not code specific)
I have this locations feature I'm working on implementing and I think I'm getting close to figuring it out but wondering on some architecture decisions.
The way everything is set up now looks like this:
I need to retrofit this. Instead of returning a URL, I need the API to return JSON data of multiple offices AND redirect. Let's look at an easy example of data I could send back to the client:
My question is, what's the best way to accomplish sending JSON data to the client and redirecting? Should I include an object like this:
And then put the office data into something like local/sessionStorage or should I put the office data in query parameters? Or am I completely off track and thinking about this wrong?
The way everything is set up now looks like this:
I need to retrofit this. Instead of returning a URL, I need the API to return JSON data of multiple offices AND redirect. Let's look at an easy example of data I could send back to the client:
My question is, what's the best way to accomplish sending JSON data to the client and redirecting? Should I include an object like this:
And then put the office data into something like local/sessionStorage or should I put the office data in query parameters? Or am I completely off track and thinking about this wrong?
A friendly place for developers to meet other devs, ask questions, get help, and just have a good time 🙂.
36,263Members
Resources
Similar Threads
Was this page helpful?
