striderwhite / scbuddysite Goto Github PK

USEFUL LINKS
https://developers.soundcloud.com/docs/api/reference#apps

We need these fields in order to make fresh API calls. Right now we are appending part of the API call URL, but this will most likely expire or might end up blocking us if we keep using the same ID.

Here is example of a API call that calls a list of a users followers, and server returns nicely in JSON format.

"https://api-v2.soundcloud.com/users/2751638/followers?offset=1501283655753&limit=200&client_id=JlZIsxg2hY5WnBgtn3jfS0UYCl0K8DOg&app_version=1501506273"

Here is URL breakdown:

https://api-v2.soundcloud.com/users/2751638/followers REST call

?offset=1501283655753 Determines where on the "list" to show followers on SoundCloud. As far as I am aware, this number decreases as you "scroll down" the page to get more followers showing

&limit=200 items returned by API. API will only give 200 at a time

&client_id=JlZIsxg2hY5WnBgtn3jfS0UYCl0K8DOg This is what we need to sniff. Seems like a special client token or id that we cant be using all the time. Going to need to find it for each user or each request.

&app_version=1501506273 Not entirely sure what this is for, but probably determines what version API calls we use. I believe this is a requirement for the URL or else we get a 401.

Two for sure:

1. Sort by follow count
2. Sort by date followed

Should be fairly simple to implement with lambdas.

Needs research

ASP.NET Page Life Cycle Overview
https://msdn.microsoft.com/en-us/library/ms178472.aspx

State Management overview
https://msdn.microsoft.com/en-us/library/75x4ha6s.aspx

ASP.NET State Management Recommendation
https://msdn.microsoft.com/en-us/library/z1hkazw7.aspx

USEFUL LINKS
https://msdn.microsoft.com/en-us/library/3hc29e2a.aspx

https://msdn.microsoft.com/en-us/library/ms178208.aspx

https://docs.microsoft.com/en-us/dotnet/standard/async-in-depth

https://msdn.microsoft.com/en-us/library/ms178208.aspx

https://docs.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/using-an-asynccallback-delegate-to-end-an-asynchronous-operation

https://docs.microsoft.com/en-us/dotnet/standard/asynchronous-programming-patterns/polling-for-the-status-of-an-asynchronous-operation

Cool reads but old
https://www.codeproject.com/Articles/10370/Processing-Long-Running-Tasks-With-Asynchronous-Ha

http://aspalliance.com/1778_Executing_Asynchronous_Tasks_in_ASPNET.all

This is so that we don't request via api everytime. This should speed up the webapp by a lot.

Wordpress? Somthing like that?

The table goes off-centered for some reason.

ASPX sucks.. So I am just going to write the site as JS/HTML/CSS using AngularJS. Now, the only thing is this project might need to be deleted and recreated, we'll see. In the meantime, we could use ASPX as a landing page or something, idk.

Give the user the ability to hit "export" and generate an excel or csv file based on their search results.