Yes. It is great that we can go in and do so much more with the new version. One thing I do is have more than one J session running, looking and comparing. To do that with the current approach I would have to set up different J sessions with different port numbers. Hadn't really thought a lot about this yet, but will play with it myself. A lot of possibilities are opening up.
On Fri, Nov 27, 2009 at 10:00 AM, Raul Miller <[email protected]> wrote: > On Thu, Nov 26, 2009 at 9:15 PM, Don Guinn <[email protected]> wrote: > > I guess I am thinking along the line of the client/server model. There is > > already a well-defined interface in jdo that it would be nice to keep a > > clean break there. Have the browser support be written in such a way it > > could reside with the application code or separated into another instance > of > > J. User's choice. This would allow making a true server supporting many > > users by spawning instances of J for each user connecting. > > I do not see the advantages you are envisioning, but you can > modify the browser support. > > jhs is defined in system/extrals/util/boot.ijs and its > definition looks like this: > > jhs=: 3 : 0 > load '~system\extras\util\jhserver.ijs' > init_jfe_ y NB. port to serve > ) > > If we start seeing useful and distinct versions > of jhserver, I imagine we can eventually refactor > it so that the versions can co-exist with a > minimum of redundant code? > > -- > Raul > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
