Don't get it

Hi David,

I think it is important to understand the Servoy licensing model. When Servoy is managing the interaction with the user, via any method, they require a concurrent license. Using headless client still causes Servoy to create a server based session and manage all Servoy resources, including automatic updates of data changes to all users (yes, even the web based users). Try it… it is really amazing! But you pay for that.

If you don’t need that level of functionality, certainly you can create separate interfaces to the same data using other technologies. Again, PHP comes to mind. But certainly there are many others.

One of our clients has chosen to have use Servoy for their internal uses of managing and reporting on all data. But they have also chosen to create a PHP based customer facing application that will utilize the same database/tables. They understand that this will require that we code many portions of the application twice, and maintain system changes, resources, business logic in two places. But truly the customer facing portion of their systems are quite minimal as compared to their internal needs. And I wonder what this customer will think when the rumored web publishing interface of Servoy is available. IMHO that changes the playing field considerably!

Best,

Rich

coulombre:
And I wonder what this customer will think when the rumored web publishing interface of Servoy is available.

Why not help spread that rumor? What is it?

I must admit, Servoy’s development schedule makes FMP’s seem glacial.
Come to think of it, FMP’s generally appears glacial without Servoy’s help.

Hi David,

Have look here for a short ruminate about Instant Publishing.

Easy to get up and running - Classic Servoy - Servoy Community

It is the original point I made ever so long ago now regarding the reasons for looking at change to the licensing model !!

Cheers
Harry

davidkachel:

coulombre:
And I wonder what this customer will think when the rumored web publishing interface of Servoy is available.

Why not help spread that rumor? What is it?

Well - we’re working on a new technology called WebDirect™. This will allow you to have Servoy generate all the JSP pages necessary to replicate your entire solution using headless client (i.e. you don’t have to write any JSP if you don’t want to). Version 1.0 of this will be in public beta within 60 days. Version 1.x will use the AJAX technology (like Google Maps) to update only the parts of the screen that change - will include onEnter, onDataChange and onLeave EVENTS in the browser (executing the same code as you have in your solution). There will be some limitations - it won’t do 100% of the things that the thin client can do - but it will be pretty close.

Any thoughts on this type of technology? Helpful? Not? Suggestions?

UPDATE!

After the very informative webinar today on “Overview of Headless Client” - I learned something new today - that directly impacts this discussion thread:

You do NOT have to “bind” the headless client to the JSP SESSION (thus spawing a new client for each visitor) - you can bind the headless client to the JSP APPLICATION - which means that you only need ONE Servoy Client License for UNLIMITED users. :D

Where would you bind to session versus application? Use SESSION BINDING when you need to setup USER-SPECIFIC things on your page (personalized colors, features, saved lists, shopping carts, etc).

Use APPLICATION BINDING for everything else!!

Hope this helps.

bcusick:
You do NOT have to “bind” the headless client to the JSP SESSION (thus spawing a new client for each visitor) - you can bind the headless client to the JSP APPLICATION - which means that you only need ONE Servoy Client License for UNLIMITED users. :D

Looks like I wasted billions of electrons complaining about nothing.

davidkachel:

bcusick:
You do NOT have to “bind” the headless client to the JSP SESSION (thus spawing a new client for each visitor) - you can bind the headless client to the JSP APPLICATION - which means that you only need ONE Servoy Client License for UNLIMITED users. :smiley:

Looks like I wasted billions of electrons complaining about nothing.

Weren’t you asking about building a shopping cart?
In this case, you’ve to bind to the JSP session anyway…

davidkachel:
Looks like I wasted billions of electrons complaining about nothing.

I think we all learned something with this thread. Thanks for bringing it up.

bcusick:
Use APPLICATION BINDING for everything else!!

Brilliant. Can you post an example of this?

david:

davidkachel:
Looks like I wasted billions of electrons complaining about nothing.

I think we all learned something with this thread. Thanks for bringing it up.

bcusick:
Use APPLICATION BINDING for everything else!!

Brilliant. Can you post an example of this?

Bind to app scope instead of session scope:

ISessionBean servoy_hc = (ISessionBean)application.getAttribute("servoy"); 
if (servoy_hc == null) 
{ 
servoy_hc = HeadlessClientFactory.createSessionBean(request,"headless_client_demo"); 
application.setAttribute("servoy",servoy_hc); 
}

bcusick:
Well - we’re working on a new technology called WebDirect™. This will allow you to have Servoy generate all the JSP pages necessary to replicate your entire solution using headless client (i.e. you don’t have to write any JSP if you don’t want to). Version 1.0 of this will be in public beta within 60 days. Version 1.x will use the AJAX technology (like Google Maps) to update only the parts of the screen that change - will include onEnter, onDataChange and onLeave EVENTS in the browser (executing the same code as you have in your solution). There will be some limitations - it won’t do 100% of the things that the thin client can do - but it will be pretty close.

Any thoughts on this type of technology? Helpful? Not? Suggestions?

Thoughts? Servoy direct to an AJAX web application? You’re kidding right?

Ummmm… nope. Not kidding. 8)

bcusick:
… will use the AJAX technology (like Google Maps) to update only the parts of the screen that change

Now you’ve got me really curious. Does this mean that WebDirect™ will represent Servoy screens as small bitmaps that are combined for display, or will the screens be displayed using vector graphics?

Come to Servoy World and all shall be revealed

So,

Firstly, If i’m correct about what i’ve read in this thread, servoy with its platform can provide infinite concurrent users’ hits to any application that is built through this platform. Correct?
Secondly, in what cost do you provide the above request for applications in any device (web, tablet, iphone, android) and for the whole Servoy product suite?

Thanks in advance.

Hi John,

Wow that’s a warp back in history: you replied to a 7 year old thread! In theory Servoy can handle an infinite number of users. I’m pretty sure that handling hundreds of thousands would provide some challenges but we’d be very interested in helping out with these challenges. We’ll contact you for pricing info separately.