Servoy Forum

Included with Servoy 2.2b2 and higher you will also find Servoy Headless Client. Read all about it in this document:
http://developer.servoy.com/docs/servoy ... client.pdf

In Servoy 2.2, weve introduced a new way to access database data and Servoy solution business logic: the Servoy Headless client.
The Servoy Headless Client (SHC) enables you to develop web browser applications that access any data hosted by a Servoy Server and also execute any method in a solution hosted on that particular server. SHC uses the built-in Apache Tomcat Servlet runner to communicate with Servoy Application Server. You can access SHC through Java Applications, Java Servlets and Java Server Pages (JSP).

This is awesome!

This is great and answers also this question:

Hi All,
I know it's possible to send a HTTP Request from within Servoy, but is it possible to send one from a webpage to Servoy where Servoy can manage the data wich is send within the request.

This is precisely the answer to this feature request:
http://forum.servoy.com/viewtopic.php?t=911&highlight=web

You guys are truly amazing. I am simply in awe. I truly believe you can do anything we ask for and that if it makes any sense, you will actually do it. Time to brush up on JSP.

By the way, I'd love to hear more about what this is most suited for or better any restrictions on scaling, load, etc. Very cool. I for one am thrilled!!!

Bob

jaleman wrote:SHC uses the built-in Apache Tomcat Servlet runner to communicate with Servoy Application Server. You can access SHC through Java Applications, Java Servlets and Java Server Pages (JSP).

Jan,
As you already know I'm not into Java (yet) but does this mean one can serve Java Server Pages (JSP) from the same machine where Servoy Server runs using Tomcat (wich is integrated in Servoy Server)?

Thanks...

Bert,

As you already know I'm not Jan but the answer is yes

Ciao

IT2BE wrote:As you already know I'm not Jan but...

You're NOT... I always thought... I guess I'm... just joking

Thanks for confirming .........

i think i may have misunderstood the headless client...

i thought/hoped that headless client was exactly the same as the normal servoy client, the only difference being that it does not need to launch the servoy client as a separate appication but instead a solution could be launched in a web browser. after reading the instructions ive began to realise this probably is not the case and would be asking quite a lot.

am i right in thinking now that a webpage would need coding for each form we would want to use in a headless client? i was hoping that if a whole solution is not easy to launch in a headless client then perhaps a tab panel with many tabs to different forms and relationships might be possible (and simple!) apologies if this seems obviously and appreciate anyone with more experience confirming the realithy headless client

many thanks

many thanks

We are working on a way for Servoy to "Publish" your solution (forms, tabpanels, portals, buttons, etc) to the web using JSP/HTML in an automatic fashion.

The "headless client" as it stands in 2.2 is a mechanism for you to code your own JSP pages to "talk" to your solutions.

Hope this clears things up.

bcusick wrote:The "headless client" as it stands in 2.2 is a mechanism for you to code your own JSP pages to "talk" to your solutions.

It's been a while since I've posted (I've been busy with those "other" environments - PHP, RB, FMP) but I am following the news. The name "headless client" struck me as funny since the visual I immediately envisioned was the headless horseman and then followed by an actual client who was headless [a cruel price for being a creative thinker].

While the term is a technical term, when used in a technical context, might I suggest something less visually disturbing on first mention? Maybe "Servoy Transparent Client" (STC)? Of course, that may sound like technology that isn't really there.

Just 2 cents worth - and if you don't collect pennies, then the advice may not be worth much.

If you really have to change the name then "Servoy Web Client" (SWC) would cover it better I think.
Just my 2 Euro cents.

Good suggestion guys. It's sort of tough to describe what the thing is.

"Transparent Client" sounds like a problem in Photoshop

It's not REALLY a "Web Client" either (in the sense that you have to use other tools to build the user interface. A real "web client" would be a way you deploy rather than the LAN Client).

Thanks for your input!

Servoy Web Conduit maybe ?

JSP Client.

Headless Client afterall it is an invisible client...