I was asked this in an interview and have not been able to find an answer. I do not know whether it refers to SOAP or REST, or whether it refers to the development or the execution lifecycle. Given this ambiguity, can you give answers for any of these possibilities?
Thank you and sorry for not being more specific.
It is not really something I can straight up answer easily; you would be better reading this document to get the full understanding.
Web Service Management: Service Life Cycle
Related
This is the question asked in interview.Please reply to this question.
I have no idea about web services.Please reply to this question why do we test webservices on different end points.Please make sure I need an answer in your own words.
Tsk tsk, if you don't know the answer to an interview question it's better off being honest and just saying that you don't know, because if I was interviewing you I'm sure I'd pick up if you don't know what you're talking about...
However for the sake of your own education: let's say we have an endpoint
test.com/api/create
although this is one endpoint, you can say there are several which can be reached with different protocols. (Think http verbs - GET, POST, PUT, PATCH...)
You probably don't want someone hitting the create endpoint with a GET protocol but only POST.
Theoretically you can test for this, but if you're going out of your way to test for these kind of things, I'd start to think you were just wasting company time rather than really testing meaningful functionality lol.
-- In many languages you define the protocol you want an endpoint to expose
Oh and be sure to mark whatever answer you use in the interview as answered ;-)
I've seen Log4cxx a bit and am confused as to what it's purpose actually is.
Originally when I saw Logger I assumed it was a key to access a system (that without it you couldn't get the information that you needed). Though looking more at it, it seems to be more of a tracking system? But a tracking system for what and what would one use as a "logger" then?
I'm sorry if this question is vague, but hence my not understanding it :p
I have found this: http://www.yolinux.com/TUTORIALS/Log4cxx.html but no one seems to give a why you use it and how it's beneficial. Can anyone give me an example? I think that's the biggest piece I'm missing.
A logger is not an authentification system. It logs (collects and saves) information, potentially in a logfile. See wikipedia for logging.
I've stumbled upon a job offer that I'm really interested in and one phrase seems to daze me a little.
Must be proficient in C++ and Trinity API (will be tested)
I have some knowledge of C++ and application programming interfaces, but I have no idea what "Trinity" refers to.
I've tried searching the internet but didn't find a decent answer that would really tell me what it actually means, or what knowledge it involves.
Any info would be very much appreciated.
This site should explain all you need to know about Trinity and the API:
http://www.trinitydesktop.org/
I was asked this question in an interview and had no idea. And I still don't. I thought they were created for this purpose, not to replace something that already exists. Any thoughts?
In oversimplified terms web services 'replaced' older RPC technologies like COM+ and CORBA
CORBA might be what the interviewer had expected you to answer. Or maybe RMI for java2java communication.
Probably the interviewer wanted to name some particular term but they improved the way different applications and systems communicate with each other.
I've heard a lot of buzz through the years about "Self Describing" web services and I'm curious what it means. I've flipped through the W3C standard and it doesn't really help.
I understand you can say "Give me this argument and call this functionality and I'll return something like this", but how is that actually helpful? How can software know what is relevant to a client given some context?
Can anyone give real world examples of this concept, and explain how it's better than some other alternative? Or maybe how useful/useless it is?
It's really designed as a standard for describing in a cross-platform cross-language manner an interface that a developer can use to develop a SOAP based way to exchange information with a web service.
Another alternative would be providing a library that provides a local interface to a blackbox communcation scheme, which is fraught with compatability/security issues.
Or providing documentation, which may be difficult to find, have compatibility issues, be out of date, or incomplete.
In short, it's very useful.