Web 2.0 Benefits - More simultaneous users

[olivierV]

@Ricardo_Cruz

Web 2 is also better at building APIs. Comparing a simple HandleURL in both versions you’ll find Web 1 response time was between 50~250ms, while in Web 2 is between 20~30ms.

Wow, this is a very big difference/improvement! what is it due to?

[Ricardo_Cruz]

I wasn’t around so I can’t comment too much, but I guess that part was refactored and rewritten from scratch.

[Ivan_Tellez]

@Mariano_Poli

I had developed a Xojo WebApp in order to evaluate students. A simple 10 questions multiple choice examination.
It was an stand alone WebApp running in a Windows server machine with enough resourses to support many more than 50 simultaneous users.
With up to 30 simultaneous students works quite acceptable, but more than that start loosing connections.

Wow, I did the same kind of app, but it had like 100-150 questions and for some topics it used images for the question and/or for the aswers. I started with 4 instances (30 users) but they got disconected, I had to double that on the spot to make it work fine (15 users), testing it later, max users was 20.

My list of bugs for web 2 is far for being solved so, havent bought a licence to test the performance in a compiled web 2 app

[Ivan_Tellez]

@Greg_O

"I need to know how fast the car is going to go if I’m towing a trailer with 20 or 30 cows in it. "

P.S. I have to keep reminding myself that you like goading people into fights instead of actually helping. I’ll go back to ignoring you again. Thanks for the reminder.

That thing about using the “I feel attacked” to avoid user valid questions is just sad. The real question made by OP and MANY more actually is:

"I know that I can go X fast towing a trailer with 20 cows with my current car. I need to know how fast the NEW CAR is going to go towing the same weight. "

[Jose_Fernandez_del_Valle]

@Ivan_Tellez

"I know that I can go X fast towing a trailer with 20 cows with my current car. I need to know how fast the NEW CAR is going to go towing the same weight. "

With the answers of @Greg_O and @Ricardo_Cruz, you can get an idea.

Speak about API only. The new speed of Web2 to replicate in less time is too important for me.

Ivan, sometimes you leave me with the impression that you want Apple-like answers. They only mention that the new iPhone has a new microprocessor that jumps from the A14 to the A15 Bionic.

Maybe this is what you want as a response from XOJO. Complete more commercial and focused sales answers. So, the interested user can see that it is worth jumping from Web1 to Web2.

The HandleURL theme is a good example.

[Greg_O]

The API speed improvements were a result of all the other back-end things that were done.

One thing that we didn’t mention here was the conversion of JSONItem. That in of itself made a huge difference in response times.

[vondes_vondes]

However, I’d like to clarify that my purpose here is not to provide biased answers or resemble the marketing approach of Apple. I’m here to provide information and insights based on my knowledge and training.

Regarding XOJO and transitioning from Web1 to Web2, it’s important to note that Web2 offers several advantages, including enhanced performance and functionality. APIs play a significant role in this transition, as they facilitate seamless communication between different software systems and enable developers to integrate various services into their applications efficiently.

The HandleURL theme you mentioned seems to be a good example of how XOJO leverages APIs to streamline web development. By utilizing HandleURL, developers can create dynamic web applications that respond to specific URL requests, making the user experience more interactive and engaging.

[Greg_O]

HandleURL is not new in Web2.