Cool @StanSimmons I was going to volunteer if it needed picking up. Should lead to good outcomes.
Iâve started a Project Page on the Wiki.
Feel free to edit it, add proposed features, add yourself to the project, etc.
Iâm making it a more generic Queue system since 3DFab has expressed interest in it as well.
@Perpetual has updated the backend portion of another project that now provides an API for RFID lookup.
Iâve posted a Python request example to the âRFID Machine Use Queueâ wiki project page.
Nice. Thank you @Perpetual.
Odd. Google has not indexed that page. Is there a link to it from somewhere else in the wiki?
...requests.request("POST"...
Iâm curious to know why POST instead of GET.
Sorry if Iâm answering the wrong question, but it looks like youâre asking if there are other pages of the wiki linked to the âRFID Machine Use Queueâ page on the wiki.
Thereâs a link on the left-hand menu, under âtoolsâ that says âwhat links hereâ, and it will tell you what all links to the page youâre looking at. In this case, nothing else links to the page âRFID Machine Use Queueâ. But I am likely misunderstanding this question.
Because Mike set the api up as a form. I suspect he could do a GET version, but this one is active today.
Nope. You nailed it.
Ah, that explains Googlebotâs failure.
No no. I was just curious. As long as it does not cause problems, and it does not, as far as Iâm concerned historical precedence is a good reason.
The wiki was definitely indexed on Jan 31 but not earlier this week. So, it looks like Iâm being impatient and Googlebot is being lazy.
Wow. Even Google wonât read our documentation. âŚ
Off the top of my head, I can think of serveral reasons why he chose POST over GET.
GET appends the form contents onto the end of the form action URL as CGI parameters. This has several inherent limitations.
Advantages of POST:
- can accept file uploads as a multi-part post
- does not store field data in the web server log files (a potential security issue)
- submitted content can be of arbitrary length (not limited to browsersâ max URL length of 2-4KB)
- submitting binary data (images, et al) is not subject to MIME-encoding issues with URLs
Iâm still working on the Laser Queue setup, and Iâve got an important step on the way to the Laser Queue functioning. Please check it out in the thread below:
Is there an update on how this project is going? Itâd be great to know that committee funds were spent wisely.