![](https://secure.gravatar.com/avatar/b4b551e2494b42e80aaacb6f573b0bd2.png?default=mp&rating=pg&size=250)
Aaron Mills
Joined
Activity
I have something along the lines of this:
case request.request_parameters.keys.first
when "new_subscription_notification"
when "canceled_subscription_notification"
deactivate_subscription params[:expired_subscription_notification]
end
But what I am finding is that the XML webhook request parameters seem to be blank. This is my first time trying to read webhook notifications.. any direction on how to correctly parse an incoming webhook would be awesome!
We are currently developing a rails application for a new startup and we are trying to determine which front end and native app technology we should combine with it.
We are looking at React JS and React Native as one option, and also RubyMotion and Emberjs as another option.
Does anyone have experience with either React Native or RubyMotion that can give us some input on their experience?
Thanks Chris that is exactly the input I was looking for!
So I have a Post model and a Category model and a User model.
So a user can have many posts and a post can have many categories. So returning a group of posts is very easy, however a post can have a variety of different content.
One post might be a blog post, while another might be a video, while another might be a poll.
Im tryin to figure out the best way to structure the data so that I can return a mixed list of post types, ranked by their number of likes, as fast as possible, with as few database calls as possible, while feeding those posts into an infinite scroll.
Should I just create a post_type field in my post model or would I be better off letting posts have child models for the different kinds of content?