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

Throttling best practices support for Sharepoint access #822

Open
ssmails opened this issue Feb 14, 2024 · 2 comments
Open

Throttling best practices support for Sharepoint access #822

ssmails opened this issue Feb 14, 2024 · 2 comments
Labels

Comments

@ssmails
Copy link

ssmails commented Feb 14, 2024

Going through the Microsoft recommendations for throttling, https://learn.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online

  1. Choose Microsoft Graph APIs over CSOM and REST APIs when possible
  2. Use the Retry-After and RateLimit HTTP headers
  3. Decorate your traffic so we know who you are (see section on traffic decoration best practice more on that below)

Appreciate any help on the below questions @vgrem

  • I have been using the lists / list items examples as references to get details for Sharepoint doc lib items, which make it super convenient to get the details and metadata about the items, thanks to this wonderful library. Are these the CSOM/REST APIs ?

  • Are there any Sharepoint examples in this library that use the Microsoft Graph APIs ?

  • Is there an example for using a context and executing queries for Sharepoint - with Retry-After and RateLimit HTTP headers as recommended above ?

  • Is there an example for executing queries for Sharepoint - with traffic decoration best practices as recommended above ?

@ssmails
Copy link
Author

ssmails commented Feb 23, 2024

@vgrem Can you please help answer this ? Thanks.

@ssmails
Copy link
Author

ssmails commented Mar 15, 2024

@vgrem appreciate any help on this ? Thanks

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

No branches or pull requests

2 participants