Added a comment: use list order for cost
authorsatra <satra@web>
Fri, 6 Jan 2023 19:36:07 +0000 (19:36 +0000)
committeradmin <admin@branchable.com>
Fri, 6 Jan 2023 19:36:07 +0000 (19:36 +0000)
doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_1_f2172080e8e3e324a739d8769dca2ed0._comment [new file with mode: 0644]

diff --git a/doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_1_f2172080e8e3e324a739d8769dca2ed0._comment b/doc/todo/Allow_for_URLs_prioritization_WITHIN___40__web__41___remote/comment_1_f2172080e8e3e324a739d8769dca2ed0._comment
new file mode 100644 (file)
index 0000000..aae4124
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="satra"
+ avatar="http://cdn.libravatar.org/avatar/d3afc58453bc273dc015254e1d9581b3"
+ subject="use list order for cost"
+ date="2023-01-06T19:36:07Z"
+ content="""
+as a starting point is order an implicit notion of cost? so could having s3 before dandi achieve the expected outcome. try s3 first then try api?
+"""]]