• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Web Services When to use and when not?

 
Ranch Hand
Posts: 674
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi there

I am making an Application.I am confused whethar I should use Web Services or not?


I have few question in mind.

1)In Which senerion I should use Web Services?
2)Where to User REST and when SOAP?
3)Why We use Web Services?
4)What are alternatives if we do not use Web Services?


Thanks



 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What is this "Application", and what does it need to interact with? TellTheDetails
 
Kishor Joshi
Ranch Hand
Posts: 674
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Application is an ERP application in there are 150-160 different users authoriation.I want to store their detail like Login Info Product Detail on Server So I want that data to come on web Service call..
 
Ulf Dittmer
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
So this is a server application for which you want to build a WS API?

There are any number of ways in which a client could access a server app; WS have the advantage of using an underlying protocol (HTTP) which is widely usable, even from within a web browser. These days the standard approach would be REST, unless you need SOAP - only capabilities like WS-Security.
 
Kishor Joshi
Ranch Hand
Posts: 674
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Yes this is a Client-Server application in which a Client can access data of a server.But Using WEB Services REST is a good approach or not?

I Mean which module I should depend on Web Services and which module not?

Their is many module in my application like Banking,Payroll,Inventory,HR...etc
 
Ulf Dittmer
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That depends on what the client is. If you only ever need to support browser clients, maybe you don't need an API because a web UI is sufficient. That's becoming rarer, though.

I'm not sure about the module question - you would add an API for those functionalities for which it is needed. Some of the ones you mention would need a lot stronger security (like banking and payroll), so you may not want to mix those logically or technically with the others.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic