It's not a question whether one can or cannot be used or there is a problem.
First of all there is a distinction, which does not allow to compare JHS and JHP head to head: JHS is an application (the session) and JHP is an SDK to build applications. You instead of saying "using JHS" to build web apps, you should say "using the same way as JHS". JHS has it's own private "SDK" to support web apps: process HTTP parameters, generate HTML, etc. JHP is just another such SDK. Besides some of the low-level CGI features shared with private JHS SDK, there is some high-level convenience functionality, such as HTML templates, which are familiar to and targeted to traditional web app developers. When JHS stabilizes it would make sense to look at its low-level web SDK and see if it could be abstracted to a common layer for both JSH and JHP, such drafted in: http://www.jsoftware.com/jwiki/CGI/Design > From: Björn Helgason <[email protected]> I am not really understanding why JHS could not be used to create forms and communicate with a J server. It is more or less doing it now. What I like to see and am (or was) expecting is having an application sending HTML forms to a browser and it would extend the forms like they are today in J6 so that the browserform can be bigger and show more in J7 (JHS) than the ordinary old forms in J6. Maybe you are talking about something bigger and more than that. What I want is more or less already there. I would like to see tables replacing grids and have HTML tables as input and output options. The JHS is already creating HTML code and sending it to the browser. I can not see where the problem is. 2010/4/5, Oleg Kobchenko <[email protected]>: > JHS and JHP serve different purposes: > > - JHS is a web-enabled J session, i.e. it runs > development tools (IDE) through web; > only in the future would it be possible to build > a web-based Window Driver (or other high-level toolkit) > to create user apps. > > - JHP is an SDK for web applications in J, i.e. it is > specifically targeted to create end-user web apps > in a traditional sense (like PHP, ASP, JSP etc.) > where J serves as the back-end engine. > > So it will still be possible to create JHP apps in J7, > but the developer may use the web-enables JHS session > instead of the desktop IDE. (There may be some other > enhancements like sticky session, as opposed to stateless CGI.) > > > > >> From: Henry Rich <[email protected]> > > It's not an exercise for me, it's a project, and Ric and Joey have > convinced me that JHS is not the way to go. > > Henry Rich > > Björn > Helgason wrote: >> I thought that using J7 and JHS as server were > the object of this exercise. >> ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
