Dropbox api for Delphi? [closed] - delphi

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 am considering using DropBox to sync user data with a delphi app. It would seem to solve lots of problems regarding security, permissions, etc... I see that there are some API samples for C#, python, etc.. Has anyone done it with Delphi, and if so, are there samples available?

The DropBox API is a generic web based API, either using JSON over HTTP or REST (also over HTTP) calling into the DropBox web server using an API key.
All language specific wrappers are just bindings around this API:
they either encapsulate the JSON over HTTP or REST over HTTP calls.
For a Delphi implementation, rolling your own JSON wrapper is probably the easiest.
There are various ways of doing JSON in Delphi.
Starting with Delphi 2010 on, it contains a native JSON implementation.
Up until Delphi 2009, you can use SuperObject for JSON.
This post from Daniele Teti and the comment thread Below it explain them both.
--jeroen

Related

Swagger like documentation for queueing and messaging like mqtt or sqs [closed]

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 3 years ago.
Improve this question
Is there any solution like swagger for documenting queueing and messaging like mqtt or sqs?
Check out AsyncAPI.
GitHub repo: https://github.com/asyncapi/asyncapi
AsyncAPI is an open source initiative that seeks to improve the current state of Event-Driven Architectures (EDA). Our long-term goal is to make working with EDA’s as easy as it is to work with REST APIs. That goes from documentation to code generation, from discovery to event management. Most of the processes we apply to our REST APIs nowadays would be applicable to our event-driven/asynchronous APIs too.
To make this happen, the first step has been to create a specification that allows developers, architects, and product managers to define the interfaces of an async API. Much like OpenAPI (fka Swagger) does for REST APIs.

Is There A Library of Public API Swagger Definitions? [closed]

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 8 years ago.
Improve this question
So I've been building a service that taps into popular APIs around the web and I've found Swagger to be a huge asset to the project. Instead of writing a ton of custom code that is difficult to maintain, I've been able to use Swagger definitions to dynamically create all my requests to the public APIs our service supports.
This has been working well for ~1 year, but we want to continue adding services to our platform and we ended up trading one maintenance burden for another. While there are a lot of public APIs out there, not many of them are nicely packaged in a computer consumable form such as Swagger.
I was wondering if anyone knew of a central location on the internet where a library of Swagger, RAML, API Blueprint, etc are stored.
If such a thing doesn't yet exist it probably should.
There's nothing yet - probably your closest thing would be ProgrammableWeb (just a generic API directory), PublicAPIs (another directory), and APImatic.io (they pull in APIs from several different sources), but there is no set collection of API Blueprint, Swagger, and RAML APIs as these are all open specs.
However, you may be able to contact the different API providers (API Blueprint - Apiary, RAML - MuleSoft, and Swagger - Apigee/ 3Scale) to see if they can provide you with the APIs created in their tools.
Good luck!

REST API iOS development [closed]

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'm having lots of trouble setting up the RestKit API to my app. I wonder if there is any other good API to make RESTful apps? I've just followed lots of tutorials and the github directory of the RestKit API, but I just can't get it up and running. I've seen that Xcode 4 is having problems importing this API.
This is an old question, Nowadays, after 4 years in iOS development I use AFNetworking: https://github.com/AFNetworking/AFNetworking
It is quite simple to start, and can be installed using cocoapods.
I use ASIHTTPRequest for RESTful client stuff in my apps.
You can use rest kit api for that.
You find the details about the rest kit in followings link
https://github.com/RestKit/RestKit
I can suggest standard iOS classes such as NSURLConnection and NSJSONSerialization.
Here is a series of posts that explains how to use Blocks to asynchronously perform Http requests against a RESTful API:
http://kerkermeister.net/series/ios-and-rest-http-connections/

Does anyone know of a good OData explorer? [closed]

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 8 years ago.
Improve this question
Our software has an OData API and we would like to package it with a good OData explorer so that developers can easily discover the properties and methods.
We have found this one:
http://www.silverlight.net/content/samples/odataexplorer/
But it doesn't work in some cases and is pretty crappy. We need something that is intuitive and polished.
LinqPad will let you connect to WCF Data Services, including OData endpoints.
The tool you are looking for is Sesame Data Browser.
It's a Silverlight application that works online.
For out-of-box application, you can use Tableau or Excel (with PowerPivot) to explorer your service and data
For web based library, you can check about datajs project which have published one ODataQueryBUilder js library recently. Refer to this blog for more detail: http://www.odata.org/blog/odataquerybuilder-a-cross-browser-javascript-library-for-building-odata-queries-3/
Hope this will help you.
I tried LinqPad recently but I found out that it's too strict on parsing OData XMLs, so making it work for some less-compliant OData services is very hard.
OData Viewer Tool worked perfectly for me (and it has a source code, which is also nice)

PC-SC Wrapper or Omnikey Sync API sample for Delphi2009 [closed]

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
The PC-SC component by nobbi.com doesn't seem to be Delphi 2009 compliant. I had to convert PChars to PAnsiChars but I still couldn't access ReaderList properly, all I could get was bunch of "|"s. So, is there any PC-SC wrapper for Delphi 2009, or a sample application of Omnikey's Sync API for Delphi? C# samples for Sync API are fine aswell, as I can use them as DLL under Delphi.
The device I'll be using is Omnikey 5321, mainly for MIFARE purposes.
That is the only framework I am aware of for Delphi. I have been keeping any eye out since as far back as 2001 and have not seen anything better.
I did some commercial SC development for the financial sector and ended up rolling my own framework for Delphi 5/7. I had the requirement to monitor card change events (insert/remove) and end up using a background thread. The solution was robust and worked very well.
The porting to D2009 should not be that difficult since the API is relatively small. Watch out for structure alignment and of course Unicode. As I recall the structure alignment required some fudging to get right (i.e. padding bytes were needed).
Best of luck!
David

Resources