B4J Question jServer REST API Design

[alwaysbusy]

This is more like a design/performance question. Suppose one has a REST API with several (hundereds?) of paths (don't make sense here, but for arguments sake):

/v1/pets/add
/v1/pets/get
/v1/pets/getoftype
/v1/pets/getwithforlegs
...

Do you guys make one handler /v1/pets/ and then a 'select case' of the sub path, or a handler for each sub path?

Would there be a performance difference?

The second option (handler for each sub path) looks like overkill to me, especially if hundereds of them are involved.

 

[Cableguy]

O guess it depends on (at least) one major prerogative...
Are these handlers known from the start of the app development or are they added as needed?
In the first case, a developers would be as at ease with a case select ensemble as with individual handlers.
In the second case, although individual handlers may seem overkill, they make the app much more scalable and versatile yet code wise very manageable.
If a particular handlers needs tweaking or simply removed, it' much more simple to do it with the second approach

 

[alwaysbusy]

They are indeed known beforehand (or our analyst hasn't done his job right ). The bit I'm concernced about is in the 'select case' option, there is one handler that must do everything. But maybe I'm overthinking it and that will not be a problem in performance...

 

[Cableguy]

You could do simple tests, by creating empty handlers that just log a meaningful phrase and another with the same amount of cases and log timings to see if there is any significant difference...
Yet dev wise, there will be a lot more work and organisational thinking needed with a case select option

(I still can't get over the fact that I'm actually trying to advise @alwaysbusy on how to do is work... I must be crazy!!)

 

[alwaysbusy]

on how to do is work... I must be crazy

I have an off day due to lack of sleep so I'm using you guys as my 'external brains' .

If you want to see something really freaky, try this website: https://inti.io/oilsjtanalytica/

Guessed my name in 15 questions...

 

[Lahksman]

If you want to see something really freaky, try this website: https://inti.io/oilsjtanalytica/

Guessed my name in 15 questions...

On my own pc it 'guessed' my name in 5 questions.
After that I logged into a server at work and it was unable to guess my name.

 

[alwaysbusy]

After that I logged into a server at work

Looks like your server has good protection! It is made by an ethical hacker from Belgium who will reveal how he does it in a couple of days. His main point is showing everyone that those 'fun question games' on facebook aren't as innocent as they seem.

 

[Cableguy]

I'm using my work phone where I also have my Google account and Facebook account and trello...
And it didn't find my name.... maybe I don' have one (?)

 

[alwaysbusy]

lol, this is how he does it appearantly (from the source code of the website):

window.fbAsyncInit = function() {
        FB.init({
          appId      : '803xxxxxxxxxx',
          xfbml      : true,
          version    : 'v2.12'
        });
        FB.getLoginStatus(function(response) {
          if (response.status === 'connected') {
            loggedIn = true;
            var uid = response.authResponse.userID;
            var accessToken = response.authResponse.accessToken;
          } else if (response.status === 'not_authorized') {
            loggedIn = true;
          } else {
            // the user isn't logged in to Facebook.
          }
        });
        FB.AppEvents.logPageView();
      };

 

[Lahksman]

It is made by an ethical hacker from Belgium

I know. I'm also from Belgium

 

[alwaysbusy]

I'm also from Belgium

We rule the world!!!

 

[udg]

lol, this is how he does it appearantly

Suspecting a trick like that, before taking the "test" I restarted my PC, cleaned up any cache and started Firefox directly with that URL.
It couldn't reveal my identity..
BTW, even if it were based on some huge "social" db it would have had low to no chance with me since I am deeply "asocial"..eheh

 

[Daestrum]

It couldn't guess mine, it kept guessing German sounding names lol.

 

[OliverA]

Do you guys make one handler /v1/pets/ and then a 'select case' of the sub path, or a handler for each sub path?

Another way is to have one handler and use the type of HTTP request to determine what to do (for CRUD, C = POST, R = GET, U = PUT and D = DELETE). Better explanation found here: https://onlinehelp.tableau.com/curr...s/REST/rest_api_concepts_example_requests.htm.

 

[Erel]

I don't think that it is a question of performance. There won't be a significant difference.

You should choose the pattern that is easier for you to implement and maintain.
I guess that it will be simpler to maintain fewer handlers as it will make it easier to share common code.

 

[icefairy333]

you can try with my WebPlus:https://gitee.com/icefairy/webplus
change to English:click the English like(on the right bottom)