Hi Rob -
Thanks for the quick response. I am basically trying to create an app that stores user profiles of two seperate entities. For example: The first type of profile would be musicians. They could register and create profiles (possibly through a website as well). They would have to log in to view their profiles of course. The second type of profiles are for venues. They would also be able to log in and view their profile. Once logged in i want to be able to match them up to schedule shows.
The way i currently envision it is that I can open the app and either register (create profile) of already have a profile that is private to only me or my band. This would require some sort of authentication. I could use a simple database stored username and password generated upon account creation, but am just not sure how the mobile device “talks” to a hosted database. In addition, im having trouble finding good examples on that type of username/password (profile) examples.
So I may be wrong, i haven’t been developing long, but it sounds like REST is what i need to explore. I have seen several articles (albeit not detailed) that reference REST as opposed to SOAP.
Just looking for a direction to go with this.
Thanks
Danimaltex