Terminology: Visit vs. Global vs. ???

Discussion:

Phil Surette

2003-01-02 15:08:30 UTC

If you want to make the transition from struts easier, I think
Visit -> Session would be a good move. I guess one of the
first things a Struts developer will do is try to figure out
where to put the session information.

You could call it 'TapestrySession' if you wanted to distinguish
it from 'HttpSession'. But IMO you could just use plain Session.
I don't see any problem with reusing the name since it is
being used to describe the same thing - this is less confusing
than using a new name to describe a well-known thing.

How about changing 'Engine' to 'RequestContext' while the
Pandora's box of name change is open?

-----Original Message-----
From: Malcolm Edgar [mailto:malcolm_edgar-***@public.gmane.org]
Sent: Friday, December 27, 2002 6:35 PM
To: hlship-***@public.gmane.org; tapestry-***@lists.sourceforge.net
Subject: Re: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???

I think Visit is quite good. Using Session or SessionBean has too much
overlap with Servlets & EJB. I dont like Global, globals are evil :)

EncodedRequest or RequestEncoding are good for me, but I worry about the
impact this may have on existing code.

Regards Malcolm

Subject: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???
Date: Fri, 27 Dec 2002 07:32:59 -0500
So, I'm revisiting the documenation and I start wondering ... maybe we
should clean up some of the terminology?
Where did "Visit" come from? It actually predates Tapestry; I was on a
project and we were killing trees with useless diagrams. I was busy
teaching the other developers about servlets and EJBs and we were on a
tight schedule. Anyway, I was pushing the idea that we should collect
information that would be used by many different parts of the application
into a central object, so that we wouldn't constantly have to
getAttribute() and downcast. I prefer keeping things strongly typed.
That started a discussion about what that central object would be called.
Somehow, we came up with Visit (i.e., it stores the information about the
user's visit). The intent with the name was to make it obvious that it was
short-term information, discarded when the user's visit to the application
ended.
Despite all that, I think calling it something else, say "Globals" (or
what? Suggestions welcome) may simplify adoption.
Also, I don't know why I came up with "Gesture". Gesture in UI terms is an
all-encompassing term for any kind of input the user can do: keypress,
mouse clicks and drags, etc. But that's not really how Gesture is used in
Tapestry, since Gesture should be used when recognizing input (something
the engine services do).
How about "EncodingOfURLAndRequestParameters"? EncodedServiceRequest?
EncodedRequest? RequestEncoding?
----
Howard Lewis Ship
http://tapestry.sf.net

_________________________________________________________________
The new MSN 8: smart spam protection and 3 months FREE*.
http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747
4&SU=
http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr
otection_3mf

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

h***@public.gmane.org

2003-01-02 15:18:32 UTC

Permalink

First, there already is a RequestContext object.

Second, I really like engine, its one of the names that 'feels right'. I
really see all the processing of requests revolving around the engine.

I didn't want to call Visit "Session" because there are so many other sessions
already, including HttpSession.

--
hlship-***@public.gmane.org

http://tapestry.sf.net

Post by Phil Surette
If you want to make the transition from struts easier, I think
Visit -> Session would be a good move. I guess one of the
first things a Struts developer will do is try to figure out
where to put the session information.
You could call it 'TapestrySession' if you wanted to distinguish
it from 'HttpSession'. But IMO you could just use plain Session.
I don't see any problem with reusing the name since it is
being used to describe the same thing - this is less confusing
than using a new name to describe a well-known thing.
How about changing 'Engine' to 'RequestContext' while the
Pandora's box of name change is open?
-----Original Message-----
Sent: Friday, December 27, 2002 6:35 PM
Subject: Re: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???
I think Visit is quite good. Using Session or SessionBean has too much
overlap with Servlets & EJB. I dont like Global, globals are evil :)
EncodedRequest or RequestEncoding are good for me, but I worry about the
impact this may have on existing code.
Regards Malcolm

_________________________________________________________________
The new MSN 8: smart spam protection and 3 months FREE*.
http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747
4&SU=
http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr
otection_3mf
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-contrib mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-contrib

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Phil Surette

2003-01-02 15:22:42 UTC

Permalink

I'm just going on the principal that things that are
the same should be named similarly.

How is a Visit different from a Session, other than
that it's the Tapestry version of a session?

How is Engine different from a request context?

-----Original Message-----
From: hlship-***@public.gmane.org [mailto:***@attbi.com]
Sent: Thursday, January 02, 2003 10:19 AM
To: Phil Surette
Cc: tapestry-contrib-5NWGOfrQmneRv+***@public.gmane.org
Subject: RE: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???

First, there already is a RequestContext object.

Second, I really like engine, its one of the names that 'feels right'. I
really see all the processing of requests revolving around the engine.

I didn't want to call Visit "Session" because there are so many other
sessions
already, including HttpSession.

--
hlship-***@public.gmane.org

http://tapestry.sf.net

was

Post by Phil Surette

short-term information, discarded when the user's visit to the

application

Post by Phil Surette

ended.
Despite all that, I think calling it something else, say "Globals" (or
what? Suggestions welcome) may simplify adoption.
Also, I don't know why I came up with "Gesture". Gesture in UI terms is

Post by Phil Surette

all-encompassing term for any kind of input the user can do: keypress,
mouse clicks and drags, etc. But that's not really how Gesture is used

Post by Phil Surette

Tapestry, since Gesture should be used when recognizing input (something
the engine services do).
How about "EncodingOfURLAndRequestParameters"? EncodedServiceRequest?
EncodedRequest? RequestEncoding?
----
Howard Lewis Ship
http://tapestry.sf.net

_________________________________________________________________
The new MSN 8: smart spam protection and 3 months FREE*.

http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747

Post by Phil Surette
4&SU=

http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr

Post by Phil Surette
otection_3mf
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-contrib mailing list
https://lists.sourceforge.net/lists/listinfo/tapestry-contrib

h***@public.gmane.org

2003-01-02 15:41:21 UTC

Permalink

--
hlship-***@public.gmane.org

http://tapestry.sf.net

Post by Phil Surette
I'm just going on the principal that things that are
the same should be named similarly.
How is a Visit different from a Session, other than
that it's the Tapestry version of a session?

Pretty good point here; the Visit is stored in the HttpSession and is used for the same thing; storing server-side state.

Post by Phil Surette
How is Engine different from a request context?

The engine provides services throughout the life of the application. RequestContext is a facade on the Servlet API objects (request, session and response).
IRequestCycle bundles up all the logic for running a single request from incoming dispatch through to response renderring and provides
services to all the component & objects along the way.

A single engine instance may be shared by multiple request cycles.

Post by Phil Surette
-----Original Message-----
Sent: Thursday, January 02, 2003 10:19 AM
To: Phil Surette
Subject: RE: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???
First, there already is a RequestContext object.
Second, I really like engine, its one of the names that 'feels right'. I
really see all the processing of requests revolving around the engine.
I didn't want to call Visit "Session" because there are so many other
sessions
already, including HttpSession.
--
http://tapestry.sf.net

was

Post by Phil Surette

short-term information, discarded when the user's visit to the

application

Post by Phil Surette

ended.
Despite all that, I think calling it something else, say "Globals" (or
what? Suggestions welcome) may simplify adoption.
Also, I don't know why I came up with "Gesture". Gesture in UI terms is

Post by Phil Surette

all-encompassing term for any kind of input the user can do: keypress,
mouse clicks and drags, etc. But that's not really how Gesture is used

Post by Phil Surette

_________________________________________________________________
The new MSN 8: smart spam protection and 3 months FREE*.

http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747

Post by Phil Surette
4&SU=

http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf