-
Notifications
You must be signed in to change notification settings - Fork 948
modified picow access point example to use lwip http server #701
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
base: develop
Are you sure you want to change the base?
Conversation
Co-authored-by: Andrew Scheller <lurch@durge.org>
<title>Pico Access Point</title> | ||
</head> | ||
<body> | ||
<h1>Hello from Pico.</h1> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this ought to say "Hello from Pico W" ? 😉
<p>Led is <!--#led--></p> | ||
<p></p> | ||
<form action="/switch.cgi" method="get"> | ||
<button name="switch" value="switch">Turn led <!--#not_led--></button> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm, rather than having the switch_cgi_handler
simply reading the LED's current state, and then inverting it, I wonder if it might be more idiomatic to do e.g.:
<button name="switch" value="<!--#not_led-->">Turn led <!--#not_led--></button>
and then have the switch_cgi_handler
read the value of the switch
parameter? (which I guess would also serve as a useful example of how to deal with GET query-parameters 🙂 )
No description provided.