You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2007/09/19 08:54:51 UTC
Component -> Slinglet?
Hi Slingers,
The "Component" name, used by Sling to designate objects that render
parts of content, is a bit confusing, especially w.r.t. OSGi
Components which are software modules.
We talked about this at work with Felix, Carsten and others, and we
agree that a more specific name would help in understanding,
describing and documenting Sling.
How about Slinglets?
"Slinglets are used by Sling to render pieces of content"
-Bertrand
Re: Component -> Slinglet?
Posted by Juan José Vázquez Delgado <ju...@gmail.com>.
Hi,
In fact, "Component" sounds too much common. I agree with the name Slinglet
(in a portlet style...)
BR,
Juanjo.
On 9/19/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>
> Hi Slingers,
>
> The "Component" name, used by Sling to designate objects that render
> parts of content, is a bit confusing, especially w.r.t. OSGi
> Components which are software modules.
>
> We talked about this at work with Felix, Carsten and others, and we
> agree that a more specific name would help in understanding,
> describing and documenting Sling.
>
> How about Slinglets?
>
> "Slinglets are used by Sling to render pieces of content"
>
> -Bertrand
>
Re: Component -> Slinglet?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/1/07, Carsten Ziegeler <cz...@apache.org> wrote:
> ...I would prefer a name which somehow tells you what this object does....
Thinking about it, our Components currently have *two* major roles, right?
1) Render a Content object (SlingRenderer role?)
2) Process an incoming request which might modify the Content
(SlingRequestHandler role?)
Maybe the two roles should be split in distinct interfaces, to make
naming easier?
Also, I just noticed that ComponentRequest, for example, makes no
reference to the Component interface. Makes me think that it could be
called SlingRequest instead, and maybe (too busy to look now) there
are other of our ComponentX types that might benefit from a similar
renaming.
Sorry if I'm not making things easier ;-)
-Bertrand
Re: Component -> Slinglet?
Posted by Carsten Ziegeler <cz...@apache.org>.
Okay, it seems that we've not found a good name yet. I think if we
can't come up with a better name, we should use Slinglet.
But I would prefer a name which somehow tells you what this object does.
And to make better optical distinction from Content it should not start
with "Co" :)
As Servlet is obviously already used what about one of these:
- Provider (the component provides/delivers content)
- Supplier
- Distributor
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Component -> Slinglet?
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Sep 19, 2007, at 4:30 PM, Felix Meschberger wrote:
> Am Mittwoch, den 19.09.2007, 15:48 +0200 schrieb Roy T. Fielding:
>> I think it might be more interesting to stay within the metaphor
>> and call them stones (to be loaded in the sling).
>
> Then what do we call the current Content ?
heh, good point. It's a pity their aren't more working parts in
a real sling. Ah, but there are ...
http://en.wikipedia.org/wiki/Sling_(weapon)
A sling is a projectile weapon typically used to throw a blunt
projectile such as a stone. It is also known as the shepherd's
sling. The sling is not to be confused with the slingshot, which
works on completely different principles.
A sling has a small cradle or pouch in the middle of two
lengths of cord. The sling stone is placed in the pouch.
Both cords are held in the hand, then the sling is swung and
one of the two cords is released. This frees the projectile
to fly in a straight line. It flies on a tangent to the circle
that the pouch makes. The sling derives its effectiveness by
essentially extending the length of a human arm, thus allowing
stones to be thrown several times farther than they could be
by hand.
The sling is very inexpensive, and easy to construct. It has
historically been used for hunting game and combat. Today it
still interests sportsmen as a survival tool and as an
improvised weapon.
Lots of good names there. But Slinglet is okay too.
....Roy
Re: Component -> Slinglet?
Posted by Felix Meschberger <Fe...@day.com>.
Am Mittwoch, den 19.09.2007, 15:48 +0200 schrieb Roy T. Fielding:
> I think it might be more interesting to stay within the metaphor
> and call them stones (to be loaded in the sling).
Then what do we call the current Content ?
But stone is ok so we might create DhryStone and WhetStone for
performance measurement :-)
Regards
Felix
Re: Component -> Slinglet?
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Sep 19, 2007, at 9:32 AM, Christophe Lombart wrote:
> I'm not (yet) the REST expert but Sling Component is not related to a
> specific concept in the REST model ?
Hmm, not really, though it should make it easier to build REST-based
models for Java because it doesn't fight against the resource mapping
ideas of REST.
> Maybe there is a term in the REST vocabulary that we can reuse.
> Otherwise, why not to be more generic like contlet ? :-)
I think it might be more interesting to stay within the metaphor
and call them stones (to be loaded in the sling).
....Roy
Re: Component -> Slinglet?
Posted by Christophe Lombart <ch...@gmail.com>.
I'm not (yet) the REST expert but Sling Component is not related to a
specific concept in the REST model ?
Maybe there is a term in the REST vocabulary that we can reuse.
Otherwise, why not to be more generic like contlet ? :-)
On 9/19/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>
> Hi Slingers,
>
> The "Component" name, used by Sling to designate objects that render
> parts of content, is a bit confusing, especially w.r.t. OSGi
> Components which are software modules.
>
> We talked about this at work with Felix, Carsten and others, and we
> agree that a more specific name would help in understanding,
> describing and documenting Sling.
>
> How about Slinglets?
>
> "Slinglets are used by Sling to render pieces of content"
>
> -Bertrand
>
Re: Component -> Slinglet?
Posted by Christophe Lombart <ch...@gmail.com>.
If I can :-)
Why not Object ?
because everything is content and a content is an object (thanks to the
OCM).
ok too bad joke ... !
Christophe
On 10/2/07, Thomas Mueller <th...@gmail.com> wrote:
>
> > a new name for Content then? :)
>
> 'Everything'. Because: everything is content ;-)
>
> Thomas
>
Re: Component -> Slinglet?
Posted by Thomas Mueller <th...@gmail.com>.
> a new name for Content then? :)
'Everything'. Because: everything is content ;-)
Thomas
Re: Component -> Slinglet?
Posted by Carsten Ziegeler <cz...@apache.org>.
Felix Meschberger wrote:
> Hi all,
>
> Based on Carstens proposal to simplify the Sling (formerly known as
> Component) API in [1] I created a JIRA issue [2] and a prototype API in
> the new sling-api project.
>
> If we go this route of simplifying the API, the discussion for a name is
> probably void, as there is no such thing as a Component anymore ...
>
Too bad, I really *love* naming discussions :( Perhaps we can search for
a new name for Content then? :)
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Component -> Slinglet?
Posted by Felix Meschberger <Fe...@day.com>.
Hi all,
Based on Carstens proposal to simplify the Sling (formerly known as
Component) API in [1] I created a JIRA issue [2] and a prototype API in
the new sling-api project.
If we go this route of simplifying the API, the discussion for a name is
probably void, as there is no such thing as a Component anymore ...
Regards
Felix
[1]
http://www.mail-archive.com/sling-dev@incubator.apache.org/msg00177.htm
[2] http://issues.apache.org/jira/browse/SLING-28
Am Mittwoch, den 19.09.2007, 08:54 +0200 schrieb Bertrand Delacretaz:
> Hi Slingers,
>
> The "Component" name, used by Sling to designate objects that render
> parts of content, is a bit confusing, especially w.r.t. OSGi
> Components which are software modules.
>
> We talked about this at work with Felix, Carsten and others, and we
> agree that a more specific name would help in understanding,
> describing and documenting Sling.
>
> How about Slinglets?
>
> "Slinglets are used by Sling to render pieces of content"
>
> -Bertrand