I've read online there are obviously SAML implementation codes that kdb+ can poggyback of, however I've seen something about qSAML but cannot seem to see any details or github on this. Does it exist?
Furthermore if not, is it best to go down the Java SAML approach. Has anyone experience with this?
Have tried to a few, but I'd like to know if something already exists in q
Related
I have been making Web apps for a while now. Mostly frontends.
I have always wanted to make fully functioning websites, and therefore, my question.
The question might be dumb, so please bear with me...
I have realized that there are two ways I can develop web apps:
1. I initialize/work with stacks (MERN, LAMP). Everything inside one folder. The
backend throws the HTML code (as far as I understand).
-----or-----
2. I make a Frontend service (localhost:3000 for React (for example)) and I create
a RESTful API (with its own endpoint, say localhost/somethingBackend or
something like localhost:8000).
My question is:
Did I understand this right ? Is this how webdev works ?
And the more important one, WHEN TO USE WHAT ?
What is faster or better ?
Normally I'd google something like this, but there's either not much Information about this, or more probable, I'm searching the wrong thing.
Please help me clear my concepts.
Thank you for reading this long post :)
Both are correct approaches.
But the first one is a more traditional approach towards web app but it comes with the difficulty of writing sensible, reusable code in it compared to writing random-looking nonsense which happens to work, along with performance and reliability issues.
Writing code with a RESTful approach is what I personally prefer. The majority of frameworks use this approach. Maintaining code between teams is easy.
Modern backends like nodejs can also throw HTML as a response(see templating engines) but as I said option 2 is always preferred.
I have been provided with a WebService with a REST Interface, implemented as a DLL.The documentation is really poor, and does not detail all the possible parameters.
Is there any way to get all the parameters that the DLL can accept without disassembling the DLL(something like a man function)?
Thanks a lot for your help!
In general you can't.
Of course you can list all functions with DLL Export Viewer and hope that you will find something like man function. But most probably you should use trial and error method here. Call functions and examine what they do.
PS: if there's a way to obtain documentation or source code, it will be the most correct way.
The short answer is "very unlikely". It really depends on how those services were implemented. If they really are REST, they should comply with the HATEOAS principle, so you should theoretically be able to navigate all the services just by following links provided by the responses. If this is true, all you need to know is the entry point of the services.
Or, there could be a WADL describing the service 'topology' (https://en.wikipedia.org/wiki/Web_Application_Description_Language).
On the other hand, if the services were not implemented this way (I won't say 'properly', but..), I am afraid you don't have many options apart from diving into the implementation.
QUESTION:
Could SPA+REST approach really improve the network loading ( and maybe performances ) in both client and server side instead of rendering html via php templates?
WHAT I'M EXACTLY ASKING ( FOR DUMMIES ) :
I'm ask if anyone has already built a project with this kind of architecture and if they had issues/improvements about performances.
THE THREAD::
I'm trying to create a modular and very scalable system that is composed by a client
written in html+javascript and different server applications , mainly written in php, that communicate with the client using REST.
Also i'm fascinated by the SPA ( Single Page Application ) concept and this is the way i would create the client that should be a social application with dynamic AJAX contents loaded in runtime.
So, as you can guess, the idea is to completely separate the html from php and keep it as "clean" as possible ( in this way i don't have to care about the server language ).
Somewhere i've read about multiple advantages of SPA, including the possibility to avoid useless loading of redundant parts of the page.
WHY I CANNOT BE MORE SPECIFIC:
i'm in "brainstorming" phase of a project so i cannot post code or ask something very very specific if i've nothing in my hands actually.
**
THE FAQ
**
THE ANSWHERE IS SUBJECTIVE?
NO I'm asking about benchmark / performances statistics ... mathematic
WHY DON'T YOU TEST BY YOURSELF?
Yes i'll do it too , and i could share my results for the community by an answere as i did before. But maybe someone else has done it better before...
After posting this question on google+ ( without additions "for dummies" ) they understood my request and i've found also a reasonable answer that is not subjective at all ( last comment):
https://plus.google.com/u/0/104873054042278826576/posts/gAhDryGxE3h
Note for the community:
i know that probably this answer will be moderated/deleted, but i feel compelled to say that the stackoverflow system has become not constructive in any way, starting from the "anonymous" and "explain - less" downvoting system. It allows people that doesn't understand the question , or just don't like it, to freely downvote without any explaination, even if a post can be really useful for other people. Moreover you can't understand you errors (if really any)
"Stack Overflow is a question and answer site for professional and enthusiast programmers."
it seems instead ( for many people i've heard ) more a massive multiplayer game where if other players love your game style, you won't be banned. i prefere the gameover at this point ;)
This question already has answers here:
Closed 10 years ago.
Possible Duplicate:
How to version REST URIs
I'm new to REST-ful API design, and I can't seem to find a consensus for how to implement API versioning in the REST-ful style. The possibilities I've come across include:
URL-based (eg. /myApi/version5/someCall)
This approach works great for both servers and clients ... but it doesn't seem very REST-ful (urls are supposed to correspond to resources, and the API version really isn't a part of the resource)
Payload-based (eg. $.ajax({data:{version:5, ...)
This approach works great compatability-wise, but:
A) The server needs to actually parse the payload to determine the version (which tends to put the version-checking logic "deeper" in than it should be)
B) Again, from what I can tell of the philosophy, this isn't very REST-ful (as I understand it, the data I POST should only be the data for the resource I want to create)
Header-based (eg. Accept application/json;version=5)
This approach was suggested here, which I've found to be an excellent resource on how to make a REST-ful API. In this particular case however I keep running in to problems, as no matter what I do I can't seem to get jQuery to send the version in the header.
Now, I'm sure I can eventually solve the jQuery issue in approach #3 if I try, but it made me think that I might be going down the wrong road with header-based versioning; if I'm having trouble, it seems likely the consumers of our API would also.
So, when creating a REST-ful API, can anyone please explain which versioning approach:
A) will work with the best with other bits of technology (browsers, frameworks, etc.)
B) implement the "REST-ful" philosophy most faithfully
C) is most common (this one's not important on its own, but it does tend to be an indicator of the first two)
In other words, what's the best way to handle versioning in REST-ful APIs?
Solution 1 seems practical and simple. For your reference twitter(api.twitter.com/2) and linkedin(api.linkedin.com/v1) uses URL Based Versioning, Google Data(&v=1.0) uses Payload Based. My hands-on experience is in URL Based versioning.
If you want to do an analysis, check this api directory
I would strongly suggest solution 1, it's clear and easy - not only that even StackOverFlow uses it: https://api.stackexchange.com/2.1/questions?order=desc&sort=activity&site=stackoverflow :)
I know that there are many API's like json,Facebook,twitter etc for developing related applications on iphone....but how to understand an API?This might be scilly question but I want to know how? what would you suggest for for a beginner?
You should find relevant documentation and read through some code examples utilizing the API.
If you are looking for information about the iphone, as the tag suggests, then read through the information here. There is an entire section dedicated to sample code. If you really can't understand how to make something work after some effort and some googling, then you can always ask on StackOverflow.
When ever I came through adding new API in my project I usually scan though documentation to find relevant topic to my project then after looking at the some sample code I usually start experimenting with the code to get the desired results and thats it because API is for short term use, you should not waste your precious time on just one API. So steps are, 1) find the relevant topic then 2) read sample code and 3) write your own code to get the desired results. 4) through away that API.
Cheers
Ayaz Alavi
If it's open source, read the code from beginning to end. Or to see why things were designed in a certain way, maybe try reimplementing parts of the API.