RE: Terminology: Visit vs. Global vs. ???
Phil Surette <[email protected]> Thu, 2 Jan 2003 10:22:42 -0500
| Newsgroups | gmane.comp.java.tapestry.contrib |
|---|---|
| Message-ID | <[email protected]> |
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C2B272.CB0455B0 Content-Type: text/plain 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: [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 ------_=_NextPart_001_01C2B272.CB0455B0 Content-Type: text/html <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12"> <TITLE>RE: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???</TITLE> </HEAD> <BODY> <P><FONT SIZE=2>I'm just going on the principal that things that are </FONT> <BR><FONT SIZE=2>the same should be named similarly. </FONT> </P> <P><FONT SIZE=2>How is a Visit different from a Session, other than</FONT> <BR><FONT SIZE=2>that it's the Tapestry version of a session?</FONT> </P> <P><FONT SIZE=2>How is Engine different from a request context?</FONT> </P> <P><FONT SIZE=2>-----Original Message-----</FONT> <BR><FONT SIZE=2>From: [email protected] [<A HREF="mailto:[email protected]">mailto:[email protected]</A>]</FONT> <BR><FONT SIZE=2>Sent: Thursday, January 02, 2003 10:19 AM</FONT> <BR><FONT SIZE=2>To: Phil Surette</FONT> <BR><FONT SIZE=2>Cc: tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</FONT> <BR><FONT SIZE=2>Subject: RE: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???</FONT> </P> <BR> <P><FONT SIZE=2>First, there already is a RequestContext object.</FONT> </P> <P><FONT SIZE=2>Second, I really like engine, its one of the names that 'feels right'. I </FONT> <BR><FONT SIZE=2>really see all the processing of requests revolving around the engine.</FONT> </P> <P><FONT SIZE=2>I didn't want to call Visit "Session" because there are so many other sessions </FONT> <BR><FONT SIZE=2>already, including HttpSession.</FONT> </P> <P><FONT SIZE=2>--</FONT> <BR><FONT SIZE=2>[email protected]</FONT> </P> <P><FONT SIZE=2><A HREF="http://tapestry.sf.net" TARGET="_blank">http://tapestry.sf.net</A></FONT> <BR><FONT SIZE=2>> If you want to make the transition from struts easier, I think</FONT> <BR><FONT SIZE=2>> Visit -> Session would be a good move. I guess one of the </FONT> <BR><FONT SIZE=2>> first things a Struts developer will do is try to figure out</FONT> <BR><FONT SIZE=2>> where to put the session information.</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> You could call it 'TapestrySession' if you wanted to distinguish</FONT> <BR><FONT SIZE=2>> it from 'HttpSession'. But IMO you could just use plain Session.</FONT> <BR><FONT SIZE=2>> I don't see any problem with reusing the name since it is </FONT> <BR><FONT SIZE=2>> being used to describe the same thing - this is less confusing</FONT> <BR><FONT SIZE=2>> than using a new name to describe a well-known thing. </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> How about changing 'Engine' to 'RequestContext' while the</FONT> <BR><FONT SIZE=2>> Pandora's box of name change is open?</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> -----Original Message-----</FONT> <BR><FONT SIZE=2>> From: Malcolm Edgar [<A HREF="mailto:[email protected]">mailto:[email protected]</A>]</FONT> <BR><FONT SIZE=2>> Sent: Friday, December 27, 2002 6:35 PM</FONT> <BR><FONT SIZE=2>> To: [email protected]; [email protected]</FONT> <BR><FONT SIZE=2>> Subject: Re: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> I think Visit is quite good. Using Session or SessionBean has too much </FONT> <BR><FONT SIZE=2>> overlap with Servlets & EJB. I dont like Global, globals are evil :)</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> EncodedRequest or RequestEncoding are good for me, but I worry about the </FONT> <BR><FONT SIZE=2>> impact this may have on existing code.</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> Regards Malcolm</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> >From: "Howard M. Lewis Ship" <[email protected]></FONT> <BR><FONT SIZE=2>> >To: "Tapestry Contrib" <tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org></FONT> <BR><FONT SIZE=2>> >Subject: [Tapestry-contrib] Terminology: Visit vs. Global vs. ???</FONT> <BR><FONT SIZE=2>> >Date: Fri, 27 Dec 2002 07:32:59 -0500</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >So, I'm revisiting the documenation and I start wondering ... maybe we </FONT> <BR><FONT SIZE=2>> >should clean up some of the terminology?</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >Where did "Visit" come from? It actually predates Tapestry; I was on a </FONT> <BR><FONT SIZE=2>> >project and we were killing trees with useless diagrams. I was busy </FONT> <BR><FONT SIZE=2>> >teaching the other developers about servlets and EJBs and we were on a </FONT> <BR><FONT SIZE=2>> >tight schedule. Anyway, I was pushing the idea that we should collect </FONT> <BR><FONT SIZE=2>> >information that would be used by many different parts of the application </FONT> <BR><FONT SIZE=2>> >into a central object, so that we wouldn't constantly have to </FONT> <BR><FONT SIZE=2>> >getAttribute() and downcast. I prefer keeping things strongly typed.</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >That started a discussion about what that central object would be called. </FONT> <BR><FONT SIZE=2>> >Somehow, we came up with Visit (i.e., it stores the information about the </FONT> <BR><FONT SIZE=2>> >user's visit). The intent with the name was to make it obvious that it was</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> >short-term information, discarded when the user's visit to the application </FONT> <BR><FONT SIZE=2>> >ended.</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >Despite all that, I think calling it something else, say "Globals" (or </FONT> <BR><FONT SIZE=2>> >what? Suggestions welcome) may simplify adoption.</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >Also, I don't know why I came up with "Gesture". Gesture in UI terms is an</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> >all-encompassing term for any kind of input the user can do: keypress, </FONT> <BR><FONT SIZE=2>> >mouse clicks and drags, etc. But that's not really how Gesture is used in </FONT> <BR><FONT SIZE=2>> >Tapestry, since Gesture should be used when recognizing input (something </FONT> <BR><FONT SIZE=2>> >the engine services do).</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >How about "EncodingOfURLAndRequestParameters"? EncodedServiceRequest? </FONT> <BR><FONT SIZE=2>> >EncodedRequest? RequestEncoding?</FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> >----</FONT> <BR><FONT SIZE=2>> >Howard Lewis Ship</FONT> <BR><FONT SIZE=2>> >[email protected]</FONT> <BR><FONT SIZE=2>> ><A HREF="http://tapestry.sf.net" TARGET="_blank">http://tapestry.sf.net</A></FONT> <BR><FONT SIZE=2>> ></FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> _________________________________________________________________</FONT> <BR><FONT SIZE=2>> The new MSN 8: smart spam protection and 3 months FREE*. </FONT> <BR><FONT SIZE=2>> <A HREF="http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747" TARGET="_blank">http://join.msn.com/?page=features/junkmail&xAPID=42&PS=47575&PI=7324&DI=747</A></FONT> <BR><FONT SIZE=2>> 4&SU= </FONT> <BR><FONT SIZE=2>> <A HREF="http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr" TARGET="_blank">http://www.hotmail.msn.com/cgi-bin/getmsg&HL=1216hotmailtaglines_smartspampr</A></FONT> <BR><FONT SIZE=2>> otection_3mf</FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> </FONT> <BR><FONT SIZE=2>> -------------------------------------------------------</FONT> <BR><FONT SIZE=2>> This sf.net email is sponsored by:ThinkGeek</FONT> <BR><FONT SIZE=2>> Welcome to geek heaven.</FONT> <BR><FONT SIZE=2>> <A HREF="http://thinkgeek.com/sf" TARGET="_blank">http://thinkgeek.com/sf</A></FONT> <BR><FONT SIZE=2>> _______________________________________________</FONT> <BR><FONT SIZE=2>> Tapestry-contrib mailing list</FONT> <BR><FONT SIZE=2>> Tapestry-contrib-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org</FONT> <BR><FONT SIZE=2>> <A HREF="https://lists.sourceforge.net/lists/listinfo/tapestry-contrib" TARGET="_blank">https://lists.sourceforge.net/lists/listinfo/tapestry-contrib</A></FONT> </P> </BODY> </HTML> ------_=_NextPart_001_01C2B272.CB0455B0-- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf