Web API Template 2.0?

[Adrian01]

Just a little request / suggestion (maybe you already had this in mind).

I just want to comment that not all API's are related to a DB (CRUD type).
So it would be nice if you let the API foundation to be easily extendable to add other use cases (not database related).

I found this article, and the first paragraph describes what I really mean.
Please ignore the title, as we all know that an API is not a DB (title is a bit offensive):

My main point is that an API lots of the times is not directly mapped to a table 1:1 CRUD operations.

Google any API, for example mandrill's API.
As you can see, there are lots of actions non db-related like exporting a list, listing ip addresses, starting the warmup process for an ip, etc.

Mailchimp Transactional API Reference | Mailchimp Developer

API reference for Mailchimp’s Transactional API.

mailchimp.com

I hope your project could include a simple sample of an api to get the time from the server, so you show non-CRUD apis are possible and people have some guidance on that

Thanks a lot
Adrian

 

[aeric]

Just a little request / suggestion (maybe you already had this in mind).

I just want to comment that not all API's are related to a DB (CRUD type).
So it would be nice if you let the API foundation to be easily extendable to add other use cases (not database related).

I found this article, and the first paragraph describes what I really mean.
Please ignore the title, as we all know that an API is not a DB (title is a bit offensive):

My main point is that an API lots of the times is not directly mapped to a table 1:1 CRUD operations.

Google any API, for example mandrill's API.
As you can see, there are lots of actions non db-related like exporting a list, listing ip addresses, starting the warmup process for an ip, etc.

Mailchimp Transactional API Reference | Mailchimp Developer

API reference for Mailchimp’s Transactional API.

mailchimp.com

I hope your project could include a simple sample of an api to get the time from the server, so you show non-CRUD apis are possible and people have some guidance on that

Thanks a lot
Adrian

This is exactly what I have posted in other thread.

Web API Template v.1.13 rules

Hi, All and @aeric Thanks for new version of the API code. And how to use the new code structure now for custom DB structure ? What files are to be edited excepting .ini-files ? Files\*.html also ? For each parameter (that should have a separate table in DB) the separate handler is needed ...

www.b4x.com

 

[aeric]

I am lazy to add all the features. So I am going to publish the first beta with the basic features.

 

[Mashiane]

I am lazy to add all the features. So I am going to publish the first beta with the basic features.

Small steps my brother, small steps, until all is done.

Perhaps let the most voted on items be your guide first, then the other items.

 

[aeric]

First beta uploaded to GitHub. The file size of the template is 2.25MB. It is bigger than before due to an admin dashboard template (AdminLTE 3) is added for demo.

[Project Template] Web API Server v2

Updates Web API Server v3 is available Version: 2.08 Description: Create Web API Server using B4X project template Database: MySQL, SQLite Sample project: Support Ticketing System If you don't want to connect to any SQL database, see MinimaList API Server For older version, see Web API...

www.b4x.com

 

[aeric]

13. A guide or tutorial on how to use

I have started to add a Wiki to the GitHub repo for version 1 and will do the same for version 2 at some point.

 

[aeric]

Do you enjoy my Web API template and Web API Client template?

I wanted to make B4X more popular by making it possible to quickly create an API server in just seconds!

After I published my version 1 of Web API, I saw some members are interested and like this project. I also received a donation from @Mashiane. After that, I don’t expect much comments about it. I am thinking there must be issues with this project.

There are many programming languages such as PHP, Python, Ruby, .NET, Java, NodeJS to name a few; to make the API backend server. Are they more superior in many ways?

Would you be interested if I create a new version which is near to production use? Would more people donate or sponsor to this project?

I have mentioned about project EndsMeet where it is targeted as a front-end and back-end framework which will be my ultimate goal. If I create a new version of Web API then it will contribute a lot to this ambitious project.

My plan of Web API template 2.0 is:
1. Add the User and Password handlers as available in jAPI project
2. Add File Upload handler
3. Improve Help handler
4. Demonstrate how to integrate the API backend with other front-end framework such as Vue, Angular, React
5. Basic Authentication
6. Use JSON Web Token (JWT)
7. Use Mini ORM (Object Relational Mapper)
8. More cleaner and configurable server startup
9. More simpler routing in custom handler
10. Scaffold a custom handler using an external tool
11. Add a database migration class
12. Add function to create a “plain” JSON response
13. A guide or tutorial on how to use
14. Add an Admin page for manage user profile, access token and models (CRUD)

( Legends: =Done = Working in progress = Not started )

Please give your opinion. Thanks!

10. Scaffold a custom handler using an external tool
11. Add a database migration class

For these 2 items, I hope it will be left for project EndsMeet.

 

[aeric]

I just want to comment that not all API's are related to a DB (CRUD type).

Yes, with Web API Template 2, no database is required (even for CRUD).