You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hop.apache.org by Matt Casters <ma...@neo4j.com.INVALID> on 2021/06/18 08:34:34 UTC
Hop Web: timeouts
Hello Hops,
Over the past couple of weeks we've slowly been fixing the last remaining
(glaringly obvious) bugs in Hop Web and I think we now have full functional
parity on Windows, Linux, OSX and Web.
That being said, there are particular challenges which still remain for Hop
web. The first and most important issue is IMO a session timeout and the
loss of work.
I've documented possible solutions in HOP-2966
<https://issues.apache.org/jira/browse/HOP-2966> and I would appreciate it
if you could offer other ideas to fix this issue. Can we make the timeout
configurable?
Please continue to test the latest versions of Hop Web. It's easy with
these commands:
*docker pull apache/incubator-hop-web:1.0-SNAPSHOT*
*docker run -p 8080:8080 apache/incubator-hop-web:1.0-SNAPSHOT*
Thanks in advance for your input.
All the best,
Matt
--
Neo4j Chief Solutions Architect
*✉ *matt.casters@neo4j.com
Re: Hop Web: timeouts
Posted by Hiromu Hota <hi...@gmail.com>.
Hi,
I agree that auto-save would be the solution for the timeout issue.
> keeping a history of all revisions of a file, separate from the user's
version control.
We may not necessarily keep different versions than the user's.
Auto-saving every 5 mins (or a user-configured interval) would be a
low-hanging and simpler solution, that would be good enough.
Thanks,
Hiromu
On Fri, Jun 18, 2021 at 2:24 AM Bart Maertens <ba...@know.bi> wrote:
> Hi,
>
> Changing the global timeout variable on the server will only delay the
> problem, so autosave seems like the way to go.
> If we're autosaving, we could think of keeping a history of all revisions
> of a file, separate from the user's version control.
>
> In addition to that, we could look at a couple of other Hop Web tweaks,
> e.g. an optional popup warning when a user closes a Hop Web browser tab.
>
> I'm sure having this parity will open up a load of new possibilities.
> Thanks for the hard work on this!
>
> Regards,
> Bart
>
> On Fri, Jun 18, 2021 at 10:47 AM Hans Van Akelyen <
> hans.van.akelyen@gmail.com> wrote:
>
> > Hi All,
> >
> > The docker container created for Hop web currently is as simple as it can
> > get.
> > It is a default tomcat and we have not really exposed any of the options
> > available both for build and for runtime.
> >
> > One of the things we can add at build and/or runtime is an option to set
> > the session timeout, default is 30 minutes and it's probably set to that
> > value at the moment.
> > We can also add other variables like url/port configuration, where the
> > environments are and so on...
> >
> > That being said, an autosave option that keeps the current working
> version
> > separately would be awesome both in the regular client as in Hop web.
> > I think we've all run into situations where the application freezes
> because
> > you want to do a preview or test a connection and you forgot to save your
> > changes beforehand.
> > Then we could ask on restart to "recover" the current working version.
> >
> > Cheers,
> > Hans
> >
> > On Fri, 18 Jun 2021 at 10:34, Matt Casters <matt.casters@neo4j.com
> > .invalid>
> > wrote:
> >
> > > Hello Hops,
> > >
> > > Over the past couple of weeks we've slowly been fixing the last
> remaining
> > > (glaringly obvious) bugs in Hop Web and I think we now have full
> > functional
> > > parity on Windows, Linux, OSX and Web.
> > >
> > > That being said, there are particular challenges which still remain for
> > Hop
> > > web. The first and most important issue is IMO a session timeout and
> the
> > > loss of work.
> > > I've documented possible solutions in HOP-2966
> > > <https://issues.apache.org/jira/browse/HOP-2966> and I would
> appreciate
> > it
> > > if you could offer other ideas to fix this issue. Can we make the
> > timeout
> > > configurable?
> > > Please continue to test the latest versions of Hop Web. It's easy with
> > > these commands:
> > >
> > > *docker pull apache/incubator-hop-web:1.0-SNAPSHOT*
> > > *docker run -p 8080:8080 apache/incubator-hop-web:1.0-SNAPSHOT*
> > >
> > > Thanks in advance for your input.
> > >
> > > All the best,
> > > Matt
> > > --
> > > Neo4j Chief Solutions Architect
> > > *✉ *matt.casters@neo4j.com
> > >
> >
>
Re: Hop Web: timeouts
Posted by Bart Maertens <ba...@know.bi>.
Hi,
Changing the global timeout variable on the server will only delay the
problem, so autosave seems like the way to go.
If we're autosaving, we could think of keeping a history of all revisions
of a file, separate from the user's version control.
In addition to that, we could look at a couple of other Hop Web tweaks,
e.g. an optional popup warning when a user closes a Hop Web browser tab.
I'm sure having this parity will open up a load of new possibilities.
Thanks for the hard work on this!
Regards,
Bart
On Fri, Jun 18, 2021 at 10:47 AM Hans Van Akelyen <
hans.van.akelyen@gmail.com> wrote:
> Hi All,
>
> The docker container created for Hop web currently is as simple as it can
> get.
> It is a default tomcat and we have not really exposed any of the options
> available both for build and for runtime.
>
> One of the things we can add at build and/or runtime is an option to set
> the session timeout, default is 30 minutes and it's probably set to that
> value at the moment.
> We can also add other variables like url/port configuration, where the
> environments are and so on...
>
> That being said, an autosave option that keeps the current working version
> separately would be awesome both in the regular client as in Hop web.
> I think we've all run into situations where the application freezes because
> you want to do a preview or test a connection and you forgot to save your
> changes beforehand.
> Then we could ask on restart to "recover" the current working version.
>
> Cheers,
> Hans
>
> On Fri, 18 Jun 2021 at 10:34, Matt Casters <matt.casters@neo4j.com
> .invalid>
> wrote:
>
> > Hello Hops,
> >
> > Over the past couple of weeks we've slowly been fixing the last remaining
> > (glaringly obvious) bugs in Hop Web and I think we now have full
> functional
> > parity on Windows, Linux, OSX and Web.
> >
> > That being said, there are particular challenges which still remain for
> Hop
> > web. The first and most important issue is IMO a session timeout and the
> > loss of work.
> > I've documented possible solutions in HOP-2966
> > <https://issues.apache.org/jira/browse/HOP-2966> and I would appreciate
> it
> > if you could offer other ideas to fix this issue. Can we make the
> timeout
> > configurable?
> > Please continue to test the latest versions of Hop Web. It's easy with
> > these commands:
> >
> > *docker pull apache/incubator-hop-web:1.0-SNAPSHOT*
> > *docker run -p 8080:8080 apache/incubator-hop-web:1.0-SNAPSHOT*
> >
> > Thanks in advance for your input.
> >
> > All the best,
> > Matt
> > --
> > Neo4j Chief Solutions Architect
> > *✉ *matt.casters@neo4j.com
> >
>
Re: Hop Web: timeouts
Posted by Hans Van Akelyen <ha...@gmail.com>.
Hi All,
The docker container created for Hop web currently is as simple as it can
get.
It is a default tomcat and we have not really exposed any of the options
available both for build and for runtime.
One of the things we can add at build and/or runtime is an option to set
the session timeout, default is 30 minutes and it's probably set to that
value at the moment.
We can also add other variables like url/port configuration, where the
environments are and so on...
That being said, an autosave option that keeps the current working version
separately would be awesome both in the regular client as in Hop web.
I think we've all run into situations where the application freezes because
you want to do a preview or test a connection and you forgot to save your
changes beforehand.
Then we could ask on restart to "recover" the current working version.
Cheers,
Hans
On Fri, 18 Jun 2021 at 10:34, Matt Casters <ma...@neo4j.com.invalid>
wrote:
> Hello Hops,
>
> Over the past couple of weeks we've slowly been fixing the last remaining
> (glaringly obvious) bugs in Hop Web and I think we now have full functional
> parity on Windows, Linux, OSX and Web.
>
> That being said, there are particular challenges which still remain for Hop
> web. The first and most important issue is IMO a session timeout and the
> loss of work.
> I've documented possible solutions in HOP-2966
> <https://issues.apache.org/jira/browse/HOP-2966> and I would appreciate it
> if you could offer other ideas to fix this issue. Can we make the timeout
> configurable?
> Please continue to test the latest versions of Hop Web. It's easy with
> these commands:
>
> *docker pull apache/incubator-hop-web:1.0-SNAPSHOT*
> *docker run -p 8080:8080 apache/incubator-hop-web:1.0-SNAPSHOT*
>
> Thanks in advance for your input.
>
> All the best,
> Matt
> --
> Neo4j Chief Solutions Architect
> *✉ *matt.casters@neo4j.com
>