https://htmx.org logo
Powered by
# htmx-general
  • m
    yeah, OK, I was wrong again, it is delaying the first request. That's wrong.
  • m
    Can you log an issue for me to fix?
  • m
    for short enough throttles people won't notice, but at 60 seconds... you'll notice
  • n
    > it is delaying the first request I actually think 
    throttle
    is delaying every request and not only the first one. It is properly throttling the events, though.
  • n
    If I setup throttling for 30s and the event gets fired more than once since it was executed, it will trigger only once but after the 30s.
  • n
    But if the event is NOT fired for 30s or more, then whenever I fire it, it will delay it for 30s even if it hasn't been fired for over 30s.
  • n
    hope that's clear.
  • n
    that seems to be my experience from testing manually for the past few hours.
  • n
    @User here's a Pull Request with a shoot in the dark to fix throttling 😛 Hope it helps: https://github.com/bigskysoftware/htmx/pull/458
  • n
    Off to bed!
  • u
    Thanks guys!
  • u
    I am going to use 'once' for now
  • t
    Does htmx have a way to trigger events or push things onto the browser history when using websockets?
  • t
    I know it's possible to do this when using regular HTTP request/response
  • t
    But I couldn't find anything in the documentation for responses submitted over websockets!
  • m
    hmmm, I don't think so, not yet.
  • m
    A good use case would be good to have for adding the feature. The API for working w/ history is bonkers, but we could surface it via the 
    htmx
    object.
  • m
    @User do websockets support some form of headers?
  • t
    My use case is that I'm building a web gui for GDB. In GDB MI mode (which is the reccomended mode for building GUIs on top of) you submit commands and listen for responses asyncronously - those responses cause bits of the UI to be re-rendered and sent back to the browser via a websocket
  • m
    wow
  • t
    But in some cases I don't necessarily want to re render the whole UI element. The source code is a good example... I just want to move the css class that causes a line to be highighted, rather than load and re-highlight the whole file and send all that
  • t
    I'd love to just trigger a bit of hyperscript that moves the css class from one line to another
  • m
    are you willing to run some bleeding edge htmx? This sounds like it might be a great driver for buffing out websocket support
  • t
    Yes, I think I would be willing to do that
  • m
    🙂 OK, let's wait for @User to check in, and come up w/ a plan
  • t
    Sounds good to me 🙂
  • m
  • m
    Right now I dont' see any notion of headers for an 
    HX-Push-URL
    but I'm sure we can add that somehow
  • t
    Yeah - it's possible to add request headers when submitting a message over websockets, right? So something similar for responses could work
  • m
    the websocket API doesn't look like it surfaces headers, but we could support JSON responses with a 'headers' and 'data' field or something like that
1...225226227...1146Latest