Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
Idea is to create multiple URL reference for a web application for each customer . (separate DB for each URL ) .
This is to create a application to various user with one solution.
Idea is to create multiple URL reference for a web application for
each customer . (separate DB for each URL ) . This is to create a
application to various user with one solution.
GORM has support for multitenancy and one of the options is to use a subdomain resolver so tenant1.yourapp.com can have a different database than tenant2.yourapp.com even if those are both the same instance of the app. More information is available at http://gorm.grails.org/latest/hibernate/manual/index.html#multiTenancy.
Unfortunately, the endpoint for API calls is not the Domain... it is the Controller. Even when you create bindings to the domain for a RESTFUL API, a controller is still dynamically maintained/created to be able to deal with the MAPPINGS for the annotations.
This doesn't solve for an RPC API solution and is only limited to a CRUD-based RESTFUL API.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have made an application with React native and the application consumes information from an api made with django rest framework.
while working with this I had a concern on how to transfer card information from the application to the api.
I configured the server to use ssl certificates, but i feel this is not enough.
My question is, what and how are the best and safe ways to pass card information from my app to the server?
I appreciate experiences and knowledge
I would suggest to not send card information to your server. Instead use one of the modern payment provides:
Stripe
BrainTree
etc (there are quite a few services that work this way)
All of these providers work a little differently to how you were thinking of taking payments:
What you do is in your frontend you send the user's card-details directly to them (Stripe or braintree etc)
they then store these securely and return to your frontend a random ID.
You can then send that to your backend (and store it)
to charge the card you hit their api asking them to charge the stored card for the ID.
This way your server never has the users card details.
If processing payments is not part of your core business, it is advised not to attempt store or process the card numbers yourself. The rules on security around handling card details are extremely complex. An example of this is the PSD2 of the European Union (for an easy to digest piece on one of the obligations, read this)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
i have crawled some data from import.io. That data are in my import.io account. I have another import.io account. Now I want to tranfer data of my previous account to my new account. How can i do it? Is it even possible? I found no option for that
Thanks in advance
Do you mean to port the actual data extracted, or the API you defined?
There is a way to port the APIs, although one by one:
Open two browser windows and log in to your OLD and NEW accounts, respectively
Click on an API inside the OLD account, and copy the URL
Paste the URL inside the NEW account window: you'll be able to "duplicate" the API in the new one. This will be a copy of the original API definition, and you will be able to run it and edit it with your new account.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
I'm going on develop web api server (php) that has an attendance feature
client need me to make fingerprint-direct-to-webserver I created
So, my question is what is the easy way to accomplish this requirement?
Does it have any Fingerprint that already be able to do this? (connected to PHP web server, or it has an API to reply what data inside it?) [If it already in market, I might not need to created it]
Does anyone ever do this before, I'm looking on some IP Fingerprint (such as BIOEntry / BioStation series), I'm little worried that, is it has some encrypted key also or not, if it has it might be problem for me. could you give the fingerprint product name?
How fingerprint send the data? (GET/POST? TEXT/XML/JSON? If you have some copy/paste of its data, it would help me alot)
Yes there some middleware solutions available to integrate fingerprint attendance with web based applications. Bio-Plugin™ is one of them that can be integrated with your web api server (php). Also encrypted key might be available now. The system send fingerprint data thorugh SOAP protocol. Hope this will help.
Almost the same web api exist in the market. API details are http://camsunit.com/application/biometric-web-api.html.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I know Apigee comes with several out of the box API to do deployments and query various pieces of information. Is there a lightweight out of the box API that we can give to our customers to verify if the APigee platform is still alive and running? This will prevent them from sending us API traffic when the system is unable to process it.
The following may be a good partial solution, but it really depends on how you intend to expose this information, where your monitoring server sits in the architecture, and what facilities you have to process/report status. That said...
Depending on what you define as 'lightweight', there is an option for OPDK installations to CURL on the following:
http://{management-server-ip}:8080/v1/servers
To check status, there is a field called IsUp (Boolean). To get more specific, you can use the query parameter type so you can get back specific components. The valid values are:
http://{management-server-ip}:8080/v1/servers/?type=app-datastore
http://{management-server-ip}:8080/v1/servers/?type=kms-datastore
http://{management-server-ip}:8080/v1/servers/?type=message-processor
http://{management-server-ip}:8080/v1/servers/?type=router
I don't believe this is possible on Cloud due to the nature of component resourcing.
If you are trying to determine whether Apigee is able to serve your own APIs, it might make sense to create a ping API call manually. You might want a couple of different flavors -- one that immediately turns around and responds from within Apigee (testing connectivity to the Apigee layer), and one that pings your backend servers (testing end to end connectivity). Anything out of the box wouldn't be able to ping your backend.
What many customers do is create a "Health Check" API Proxy.
This can just be an Echo Server, which you can easily create by building an API Proxy with No Target.
In the New API Proxy tool, choose (o) No Target. And that's it.
Then whatever data you pass to that proxy will be returned in the response.
For example:
$ curl http://{your-org}-{env}.apigee.net/v1/healthcheck -d "Hello"
Hello
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Would it be best to read from gmail via pop3/imap? Or should/must I use an http script that actually logins in via web interface and gets all the emails that way?
Also, I would like to iterate this question for:
live
hotmail
[any other major web mail provider]
To read incoming messages, you should use POP or IMAP.
To send messages, you should use SMTP.
Your choice of protocol depends on what you're trying to do and what the mail provider supports. (Gmail supports all three)
Use POP if you want to process all incoming messages without affecting them elsewhere.
Use IMAP if you want to manipulate the messages on the site (eg, to move them into folders).
Use SMTP to send email.
Manually scraping a webmail site (especially a modern AJAXy webmail site) is a recipe for disaster.
POP or IMAP will be standard for a long time; you would certainly have to make ongoing compatibility changes to an http script. Besides being barbaric.
Also, remember SMTP is for sending mail, not reading it.