RE: Terminology: Visit vs. Global vs. ???

--
[email protected]

http://tapestry.sf.net
> 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.


> 
> 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.


> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Thursday, January 02, 2003 10:19 AM
> To: Phil Surette
> Cc: tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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.
> 
> --
> [email protected]
> 
> http://tapestry.sf.net
> > 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:[email protected]]
> > Sent: Friday, December 27, 2002 6:35 PM
> > To: [email protected]; [email protected]
> > 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
> > 
> > >From: "Howard M. Lewis Ship" <[email protected]>
> > >To: "Tapestry Contrib" <tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
> > >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
> > >[email protected]
> > >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
> > _______________________________________________
> > Tapestry-contrib mailing list
> > Tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> > https://lists.sourceforge.net/lists/listinfo/tapestry-contrib


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