It will never end up. I was sooo happy not being in XoJo stuff anymore. But again we have a customer with XoJo application. We can’t rebuild everything in one time cause we first have to rebuild the servers and within that there is the need to further development of their applications for iOS and Android. This will be replaced when the WebServer is running. The Idea of their WebApp isn’t bad, they do their sales. But what they did not see: they grow. And this makes it a bit complex. While the Webserver is running as XoJo application and they have too many visitors on their site. And many problems more. But people making really nice pieces of software with xojo. Now it will become something else. Runtime of three years.
2 Likes
Though I haven’t used Xojo, I’ve seen enough references to bottlenecks with web deployment that I’ve been curious how that works.
Their docs are somewhat vague, but do note that a single instance is running persistently for all connections (assuming no load balancing, of course).
Without having seen the thing firsthand, the descriptions offered leave me scratching my head about what it’s actually doing.
Is it rendering into a canvas within the browser, using a method somewhat like screen sharing?
It doesn’t seem to be delivering stateless HTML.
Can you help a noob understand what’s happening mechanically with a Xojo web app, or help me find where the mechanism is described in technical terms?
it is a cooperatively threaded single EXE that delivers HTML + custom JS & CSS to a browser
That JS then sends “events” back to the server which you can respond to in Xojo code that runs mostly server side
You can actually download it and try it locally without spending a cent just to tinker about
Because its a single EXE heavy loads really require some kind of load balancer in front of it like nginx etc which is what they use on their Cloud service
Or that you can set up for yourself using a nice tool like LifeBoat so you achieve a “cloud” service without the costs that Xojo cloud has
Others may chime in here as well