News for hackers. Stuff that matters.

ortne

Thanks for the advice! This seems like a reasonable approach I might give a test drive.
Ah interesting! Thanks for the reply, seems like you're having to deal with a lot more variability than me. Definitely sounds like an interesting problem and interesting solution to match.
I would most likely want to manage them as a single code base as the business logic among the various states would be largely common (upwards of 80% or higher).

Ask HN: How would you an API to handle request variability by US state?

I have been struggling with determining a sane approach to building a REST API for servicing each state within the United States. Effectively, it would be creating the same semantic resource/operation for each state, but the input/attributes of that resource slightly vary by state. Some states are nearly identical and others are drastically different.One option I have tried in the past is...

( Read More... | 8 comments | 9 points | on HN )