Terminology: Visit vs. Global vs. ???

[Howard M. Lewis Ship]

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
hlship-***@public.gmane.org
http://tapestry.sf.net

[Scot Doyle]

I just read the docs for the second time. Here are
the terms I most confusing at first blush...

parameter
in (in what?, it seems relative not descriptive)
gesture

Maybe session would be a better word than visit, but I
guess we have to avoid using servlet words?

Scot

Post by Howard M. Lewis Ship
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

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


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

[Richard Lewis-Shell]

Maybe you should just include that defn of Visit in the docs (or is it
there already?). I think 'Visit' is a good way of describing what it
is - as long as Tapestry has its own session type object, Visit works
for me...

Re: Gesture:
ServiceRequestEncoding? LinkEncoding (matches well with the components
that do the rendering)?

R

On Saturday, December 28, 2002, at 01:32 AM, Howard M. Lewis Ship

Post by Howard M. Lewis Ship
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
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

[Geoff Longman]

I like Visit and Gesture as they are, thank you very much! :-)

Geoff
----- Original Message -----
From: Richard Lewis-Shell
To: tapestry-contrib-5NWGOfrQmneRv+***@public.gmane.org
Sent: Friday, December 27, 2002 4:23 PM
Subject: Re: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???


Maybe you should just include that defn of Visit in the docs (or is it there already?). I think 'Visit' is a good way of describing what it is - as long as Tapestry has its own session type object, Visit works for me...

Re: Gesture:
ServiceRequestEncoding? LinkEncoding (matches well with the components that do the rendering)?

R

On Saturday, December 28, 2002, at 01:32 AM, Howard M. Lewis Ship wrote:


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
hlship-***@public.gmane.org
http://tapestry.sf.net

[Malcolm Edgar]

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=7474&SU=
http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspamprotection_3mf



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