Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update out-of-scope content on homepage #12

Open
ajo2995 opened this issue May 2, 2019 · 2 comments
Open

update out-of-scope content on homepage #12

ajo2995 opened this issue May 2, 2019 · 2 comments

Comments

@ajo2995
Copy link

ajo2995 commented May 2, 2019

The standard can't enforce performance claims, so maybe replace/remove "optimized for speed".

Also, the data transfer use case is not there yet (until v2 POST/PUT specs are defined)

@jacklagare
Copy link
Contributor

I agree with this. The standard may be designed in such a way that it promotes good performance but some implementation can mess it up and make even a simple call perform badly. Promoting "ease of data transfer" would be more appropriate I guess?

My understanding with the data transfer use case is that someone can build a client that connects to Server A, extracts data, and save it in their own database. Using that same client, it can then connect to Server B and do the same thing.

@BrapiCoordinatorSelby
Copy link
Member

I reworded the "Optimized for Speed" section to the following

A lot of effort has been invested to make BrAPI an efficient data model without compromising flexibility. Implementations can be tuned to fit the scale of the database.

Let me know what you think, or if it still needs to just be taken out.

And V2 is out now, so data transfer makes sense now :)

Sorry this took a year to fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants