Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of ekoneil@gmail.com designates
 64.233.184.195 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=EOr/kuRjpsdgG1Qp/X3W5+Drv7rGkk9yEbG+cbW/gRljIdtG5jrS6NJtRGcCwfkr0NACIKBMeElr23zRYjEPnqUtyVXTITgNf/n/bZJOp7eBHdKPAFVblIfN2vdN8Q5peAD/EkOdUy8zV4fed+Pe/hMa9LaWTl1GC1Z5vz9fngE=
Message-ID: <e9ac835405070815106285659a@mail.gmail.com>
Date: Fri, 8 Jul 2005 15:10:17 -0700
From: Eddie ONeil <ekoneil@gmail.com>
Reply-To: Eddie ONeil <ekoneil@gmail.com>
To: Beehive Developers <beehive-dev@incubator.apache.org>
Subject: Re: netui-core module
In-Reply-To: <42CED4BB.30608@bea.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <42CEC6EF.4030808@gmail.com> <42CEC91E.5040900@bea.com>
	 <42CECC7B.8090603@gmail.com>
	 <40f0265405070812097291d7c2@mail.gmail.com> <42CECFC6.8020003@bea.com>
	 <42CED4BB.30608@bea.com>

Rich--

  How about just moving the urltemplating code that requires scoping
into the src/pageflow source module?  This wouldn't require a new
source module and doesn't change any dependencies, though it does
break a package across modules (which isn't terrible).

  Thoughts?

Eddie


On 7/8/05, Richard Feit <richard.feit@bea.com> wrote:
> I caused a lot of confusion with my arrows.  :)  Those arrows meant
> "depends on", but that's not how most people outside of me would view
> it.  Reversing them, you get:
>=20
>     util -> scoping -> core
>=20
> ...where before, it was:
>=20
>     scoping -> util
>=20
> ...which meant that util depended on scoping.  That dependency was in a
> class in org.apache.beehive.netui.core, which would now live in a "core"
> module.
>=20
> Rich
>=20
> Eddie O'Neil wrote:
>=20
> >
> >   And, we still have to split the "netui.util" package across the
> > "util" and "core" packages because the Logger and
> > InternalConcurrentHashMap classes live in "netui.util".  Moving
> > "netui.core" isn't sufficient, right?
> >
> > Eddie
> >
> >
> >
> > Daryl Olander wrote:
> >
> >> What about reversing the order of Scoping and Util?  What in Util has
> >> dependencies on Scoping?
> >>
> >> On 7/8/05, Rich Feit <richfeit@gmail.com> wrote:
> >>
> >>> Right, exactly.  I'd move org.apache.beehive.netui.core.* from util
> >>> into
> >>> core (and I agree about "core" vs. "netui-core").
> >>>
> >>> Rich
> >>>
> >>> Eddie O'Neil wrote:
> >>>
> >>>
> >>>> Rich--
> >>>>
> >>>>  Things like the Logger and InternalConcurrentHashMap are in
> >>>> netui.util, so would you propose splitting netui.util across the two
> >>>> modules:
> >>>>
> >>>>  netui-core
> >>>>  util
> >>>>
> >>>> What specific util classes would you move into a core module?
> >>>>
> >>>> Also, how about just calling it "core" rather than "netui-core"?
> >>>>
> >>>> Eddie
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> Rich Feit wrote:
> >>>>
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> I'd like to split out org.apache.beehive.netui.core.* into a separa=
te
> >>>>> module: "netui-core".  This will allow the following string of
> >>>>> dependencies:
> >>>>>   netui-core -> scoping -> util
> >>>>>
> >>>>> Currently, the order is:
> >>>>>   util -> scoping
> >>>>>
> >>>>> Which, in addition to being weird, is limiting for scoping because =
it
> >>>>> can't use any of the basic util classes like Logger, the
> >>>>> concurrent-read-map class, etc.  Let me know if you have any other
> >>>>> thoughts about this.
> >>>>>
> >>>>> Rich
> >>>>>
> >>>>
> >>>>
> >>
> >
> >
>