hello i've been playing around with the java client run by vncserver and running my wx apps over it. basicly i have a web front end that spawns a new instance of vnc server (if one isn't running for that user already) on a successful login and takes them automagicaly to the vnc java viewer which knows to auto load the app for them
they can then interact with the application via the web client without the need for native clients and updates are a snap.
i have however hit one snag, and it's a rather big one - the java client will randomly hang, and it'll almost always hang as soon as i start playing with threads. the gui for the app will stop responding without any error that i can see.
the thing is about 90% stable... but no one wants a car that only starts 90% of the time so any insight you guys can give me into this would be handy.
Timothy Smith wrote:
hello i've been playing around with the java client run by vncserver and running my wx apps over it. basicly i have a web front end that spawns a new instance of vnc server (if one isn't running for that user already) on a successful login and takes them automagicaly to the vnc java viewer which knows to auto load the app for them
they can then interact with the application via the web client without the need for native clients and updates are a snap.
i have however hit one snag, and it's a rather big one - the java client will randomly hang, and it'll almost always hang as soon as i start playing with threads. the gui for the app will stop responding without any error that i can see.
the thing is about 90% stable... but no one wants a car that only starts 90% of the time so any insight you guys can give me into this would be handy.
What platform is the app running on? Do your worker threads make any calls to wx methods or functions other than wx.CallAfter, wx.PostEvent, or wx.WakeUpIdle?
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Robin Dunn wrote:
Timothy Smith wrote:
hello i've been playing around with the java client run by vncserver and running my wx apps over it. basicly i have a web front end that spawns a new instance of vnc server (if one isn't running for that user already) on a successful login and takes them automagicaly to the vnc java viewer which knows to auto load the app for them
they can then interact with the application via the web client without the need for native clients and updates are a snap.
i have however hit one snag, and it's a rather big one - the java client will randomly hang, and it'll almost always hang as soon as i start playing with threads. the gui for the app will stop responding without any error that i can see.
the thing is about 90% stable... but no one wants a car that only starts 90% of the time so any insight you guys can give me into this would be handy.What platform is the app running on? Do your worker threads make any calls to wx methods or functions other than wx.CallAfter, wx.PostEvent, or wx.WakeUpIdle?
it's running off freebsd, but using the vncserver any platform can view it.
i found the problem, it's actually just my code
works like a charm now. with a little more testing and modificatin i can roll out applications to venues with zero setup
Timothy Smith wrote:
it's running off freebsd, but using the vncserver any platform can view it.
i found the problem, it's actually just my code
works like a charm now. with a little more testing and modificatin i can roll out applications to venues with zero setup
Sounds very interesting; now that it's working well, would you be willing to describe it in a bit more detail?
···
--
Don Dwiggins
Advanced Publishing Technology