You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by "dave2wave (via GitHub)" <gi...@apache.org> on 2025/11/08 17:59:58 UTC
[I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
dave2wave opened a new issue, #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306
Let's discuss if using a WS on certain forms might improve UX.
1. During the Compose phase while Checks are running a WS could return each result as the check completes.
2. During the Vote phase as votes are seen in the email thread the form can register each vote.
3. When we add Distributions as each completes the result could be pushed.
Seems like a good time to have this discussion since we are refactoring all of the forms
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3506762865
Alternatively these forms could automatically refresh after N seconds.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #306: Discuss if WS might improve the UX for certain forms
URL: https://github.com/apache/tooling-trusted-releases/issues/306
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3519326100
Another concern is that for the last two days the **ASF pubsub** has been unreliably slow.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3519351982
Another future use of **pubsub** could be to listen for commits to the svn dist release area (although periodic `svn up` is probably fine.)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "gstein (via GitHub)" <gi...@apache.org>.
gstein commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3507546857
To reduce load/connections, maybe only use WS on authenticated pages. ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "gstein (via GitHub)" <gi...@apache.org>.
gstein commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3511516204
I'm working pypubsub right now to add websocket protocol handling. Note that its normal http(s) client connections are persistent chunked connections, just like SSE.
Seems the only issue here is the framing/packaging of the pubsub events, meaning that ATR could use the ASF's standard pubsub server, if it packaged the payloads properly. (note that pubsub already has two formats for payload delivery; third format (SSE) should be "simple")
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3519330406
To really digress. It may be that ATR will produce **Release LifeCycle Events** to a **pubsub topic** with a subtopic for each PMC.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "sbp (via GitHub)" <gi...@apache.org>.
sbp commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3507892682
We don't need duplex, so we'd more likely use [SSE](https://en.wikipedia.org/wiki/Server-sent_events).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "gstein (via GitHub)" <gi...@apache.org>.
gstein commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3514926239
Yes, websockets.
Two asfquart-based apps (BAT and asfmm) use websockets. I investigated adding improved support to asfquart, but decided on improving pypubsub instead. The question about WS for use in ATR (another asfquart app) thus arose, and we now have this issue.
I think SSE can be added to pypubsub, too. Then it would just be a decision for ATR to use pubsub.a.o for event flow.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3559910024
OK. We have consensus on what approach to use when.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3519323146
Here is how I view these the choices.
1. Use a **pubsub** central service event feed when you have multiple distinct producers.
2. Use a **pubsub** central service event feed when you have multiple distinct consumers and a single service api is infeasible.
3. Use **WS** if your consumer needs a duplex conversation with the producer.
4. Use **SSE** if your consumer needs to receive simplex data from a single producer.
If you really need **pubsub** then you should also consider any of Kafka, Pulsar, ActiveMQ, Artemis, etc.
The answer here is that **SSE** is probably what ATR should use to communicate server side results to a web page.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "gstein (via GitHub)" <gi...@apache.org>.
gstein commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3519590390
To pull together several replies to the above comments:
* a single service API is naturally polling, whereas pubsub, SSE, and WS are event-driven
* if you have an issue with ASF pubsub, then ask Infra what happened; it shouldn't be dismissed, IMO
* I think third parties would like to see pubsub events, but I'm totally guessing
* iirc, isn't the svn dist area going away? If it will remain for a while, then yes: I agree during the transition that listening to events would be important for ATR
* the question about a replacement for pubsub.a.o is for Infra. The suggested alternatives are Java-based, which is generally not on the easy-approval list for Infra's services
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org
Re: [I] Discuss if WS might improve the UX for certain forms (tooling-trusted-releases)
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on issue #306:
URL: https://github.com/apache/tooling-trusted-releases/issues/306#issuecomment-3512458060
I assume WS = Websockets (from the context). I think WS is only really useful when you have some data streaming but when you have "small number of users" (relatively - in 100s) and just "forms", long pollin, timed refresh or SSE as mentioned by @sbp approach should do just fine and is far easier to deploy and secure in general. We had similar discussion in Airflow which has very similar usage patterns (relatively small number of users, but a need for interactive and "snappy" UI) and we never found the need to use websockets.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org