Should I Create an API or Webservice ?

views:

144

answers:

Should I Create an API or Webservice ?

Currently I am working on an app property website. Now currently if the user wants to upload a new establishment he has to enter the property details in their in house system and seperately on a different website linked to the website front end.

So we would like to eliminate this duplicate data entry. We would like to provide a webservice/api from the webbased system so that they dont have to log in into the webbased system and manually enter the details a second time.

Anyone have any ideas regarding this problem ?

They don't have to be seperate things. If you have a Web application...you're API can be Web Service based. It will provide the functionality to the consumers who will then connect to and use your web service in their application.

Justin Niessner 2009-07-08 15:07:02

OK thanks for your reply.What would my web service look like then, for example would I have to accept some XML data from them containing the data they entered in the internal system which is sent over at certain times and I write some script to import this into my DB ?

2009-07-08 15:09:55

Personally, I would create a service that accepted the property description, some identifying info about who is submitting the info, and the image (serialized to be sent across the web). You can then do whatever you need with the data to get it into your database.You should probably think about some kind of authentication too (so not just anybody can submit data).

Justin Niessner 2009-07-08 15:19:39

Well I just thought a XML would be easier to i could ensure they entrire all the data required for the web side i.e match with my DB columnslike i.e<propertyName><propertyName><address></address><description></description> etcActually how would Images work...I guess they would have send me the link of where they uploaded the image ?

2009-07-08 15:28:05

If you users aren't directly connected to the same network as your web app then providing a secure web service will probably be your best option. This would be a service they can consume in the own applications that can be used to create/amend/delete their entries on your website.

Andy Rose 2009-07-08 15:09:47

I would somehow figure out a way to do both. Either make the API web-based or make the web service use the API. This way the codebase is basically in one place and you can mix and match what users/customers want to use.

I'd probably go with making the web service a wrapper to the API.

Cody C 2009-07-08 15:13:11

ansaurus

tags:

views:

answers:

Should I Create an API or Webservice ?

related questions