On Tuesday, July 17, 2018 at 7:46:59 PM UTC-4, Bert JW Regeer wrote:
>
> The threads that run the WSGI app are pre-spawned, they wait on a new
> request to be added to a queue, peel one off, pass it down the WSGI app,
> and then back.
> ...
> What are you trying to do with a "max requests"?
>
The threads that run the WSGI app are pre-spawned, they wait on a new request
to be added to a queue, peel one off, pass it down the WSGI app, and then back.
There are no other "workers". The rest is a simple asyncore loop, whereby
requests are accepted, and added to the list of sockets to liste
does anyone know if the workers in waitress are spawned as-needed for each
request, or if they are pre-spawned and answer requests when available?
I think it is the latter. if so, is there a reasonable chance of having a
max-requests feature implemented (or would this be possible to kludge
tog
thanks for the explanation.
En 17 de julio de 2018 1:17:03 p.m. Jonathan Vanasco
escribió:
On Tuesday, July 17, 2018 at 12:45:26 AM UTC-4, jg...@live.com.mx wrote:
so, to make this clear to me: the POST made from javascript is not equivalent
to a POST made in html, the hmtl POST automatically
On Tuesday, July 17, 2018 at 12:45:26 AM UTC-4, jg...@live.com.mx wrote:
> so, to make this clear to me: the POST made from javascript is not
> equivalent to a POST made in html, the hmtl POST automatically refreshs
> page or something like that?
>
This may sound confusing... but their "equiva
@steve.percy
i did what you suggest,i passed the params in the query, retrieve them in the
home view and place them in the template, but it is the same. maybe i did not
explained myself: the page does not render at all, it shows "print" message in
the view callable, it shows as xhr in the browse
@steve.percy
i did what you suggest,i passed the params in the query, retrieve them in
the home view and place them in the template, but it is the same. maybe i
did not explained myself: the page does not render at all, it shows "print"
message in the view callable, it shows as xhr in the browse
Thanks for your recommendation. I have outlined my issues with the retail
form approach in the previous response to Steve Piercy, but I would
appreciate if you could point me to an example of some sort for rendering
the submit button (possibly even the form element itself) separately. I was
hav
Yes, I have looked at the retail form documentation. I think it's possible
to do what I want with it, but it doesn't seem very practical. Writing my
own widget might be the the best approach if I understand things correctly.
Just in case, the issue I had with the retail form approach was that I
https://docs.pylonsproject.org/projects/deform/en/master/retail.html
might be what you're looking for.
IIRC the button is also just an ordinary field of the form, which can be
rendered the same way.
HTH,
Andreas
On 17 Jul 2018, at 13:17, Tom Andrews wrote:
I'm trying to construct a treevie
I'm not sure I follow your current approach.
Have you looked at Writing Your Own Widget?
https://docs.pylonsproject.org/projects/deform/en/master/widget.html#writing-your-own-widget
Do you want to use a checkbox or a checkboxchoice?
http://deformdemo.repoze.org/checkbox/
http://deformdemo.repoze
the issue is in your javascript; the browser will never render the template
on this setup.
when you view /test via GET (or missing one or more required POST items),
templates/jg.pt is rendered.
when you view /test via POST with both variables present, the response is a
redirect (HTTPFound)
you
Hello,
I'm trying to construct a treeview-like structure with checkbox widgets
from deform and have all of the checkboxes as part of one form. If I just
render the form normally and pass the generated html to my template, I'll
obviosuly not get the structure I want.
So far I've tried to pass t
13 matches
Mail list logo
