visiting http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb and looking at apache logs, shows
XXX - - [05/Aug/2021:17:05:10 -0400] "GET /dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb HTTP/1.1" 200 18792
XXX - - [05/Aug/2021:17:05:18 -0400] "GET /dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb HTTP/1.1" 200 18792
with I guess first one to display details, and then 2nd one appears shortly after a spinner in Python tab stops spinning so - for that Python session? ... For a more sizeable http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb - the same effect of two full 286MB download requests.
XXX - - [05/Aug/2021:17:10:55 -0400] "GET /dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb HTTP/1.1" 200 299000608
XXX - - [05/Aug/2021:17:11:28 -0400] "GET /dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb HTTP/1.1" 200 299000608
It seems that ideally it should be avoided, and a singular GET should be sufficient.
visiting http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000027/sub-RAT123/sub-RAT123.nwb and looking at apache logs, shows
with I guess first one to display details, and then 2nd one appears shortly after a spinner in Python tab stops spinning so - for that Python session? ... For a more sizeable http://nwbexplorer.opensourcebrain.org/nwbfile=https://datasets-dev.datalad.org/dandi/dandisets/000005/sub-anm184389/sub-anm184389_ses-20130207_behavior+ecephys.nwb - the same effect of two full 286MB download requests.
It seems that ideally it should be avoided, and a singular GET should be sufficient.