Eric Iverson <eric.b.iverson@...> writes:

> 
> There isn't a 'main intended use'. Jsoftware tries to provide core
> facilities. What you see in J7 is what you get. No secret plan or agenda.
> We've provided a base that allows the the community to move in various
> interesting directions.
> 
> On Thu, Mar 17, 2011 at 1:41 AM, saul berg <sbaker8688@...> wrote:
> 
> > i have been using j for a few years now.  i have mulled the idea for a
> > while to
> > develop a "web framework" targeting j, and/or an apache (or other) server
> > module
> > which would allow j to be used within the server.  (by the way, i am
> > assuming
> > that none of these exist - correct me if i am wrong).
> >
> > at any rate, i recently downloaded the j701 and gave it a whirl.  at the
> > risk of
> > asking a dumb question, what is the "main intended use" of the new system?
> >  for
> > instance, is the intention to make j easier or better for use in web
> > applications?  is the intention to make it easier to turn j into a general
> > purpose web server?  is the intention just to have a front end for the
> > future?
> >
> > the reason i ask is because of the first paragraph, i.e. i don't want to
> > reinvent the wheel, or set off on some path that j701 is duplicating or
> > will be
> > duplicating.
> >
> > thanks.
> >
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
> >
> 


perhaps i didn't ask the right question.  you say "what you see is what you
get."  perhaps my question should be "what am i seeing?"  am i seeing a new
front end gui?  a web server?  something that functions (or could function) like
an apache "mod_j"?

put it this way.  i don't want to go off writing the next "mod_j" if j7 is
essentially that.  "what exactly is j7?" must sound like a dumb question, but i
actually couldn't find any documentation answering this question adequately for
me.  i know it's a new front end - that's obvious.  i know it has to use a web
server to deliver that front end - that's obvious.  all the other stuff is less
obvious, i.e. is the web server portion just something small and light duty with
the main purpose being to deliver the front end to the browser, or is it
something that is intended to compete with apache?  is this thing already
essentially creating the ability to embed j in web pages (obviously there is j
somewhere, obviously there is a web page i'm looking at, but the rest is unclear
to me), or is a "mod_j" still needed?  etc.

thanks.

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to