Terminology: Visit vs. Global vs. ???
"Howard M. Lewis Ship" <[email protected]> Fri, 27 Dec 2002 07:32:59 -0500
| Newsgroups | gmane.comp.java.tapestry.contrib |
|---|---|
| Message-ID | <005b01c2ada4$175392b0$3dc41e42@howardczkz2sl3> |
This is a multi-part message in MIME format. ------=_NextPart_000_0058_01C2AD7A.2E621370 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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? =20 ---- Howard Lewis Ship [email protected] http://tapestry.sf.net ------=_NextPart_000_0058_01C2AD7A.2E621370 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2719.2200" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>So, I'm revisiting the documenation and = I start=20 wondering ... maybe we should clean up some of the = terminology?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Where did "Visit" come from? It = actually=20 predates Tapestry; I was on a project and we were killing trees with = useless=20 diagrams. I was busy teaching the other developers about servlets = and EJBs=20 and we were on a tight schedule. Anyway, I was pushing the idea = that we=20 should collect information that would be used by many different parts of = the=20 application into a central object, so that we wouldn't constantly have = to=20 getAttribute() and downcast. I prefer keeping things strongly=20 typed.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>That started a discussion about = what that=20 central object would be called. Somehow, we came up with Visit = (i.e., it=20 stores the information about the user's visit). The intent with = the name=20 was to make it obvious that it was short-term information, discarded = when the=20 user's visit to the application ended.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Despite all that, I think calling it = something=20 else, say "Globals" (or what? Suggestions welcome) may = simplify=20 adoption.</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Also, I don't know why I came up with=20 "Gesture". Gesture in UI terms is an all-encompassing term for any = kind of=20 input the user can do: keypress, mouse clicks and drags, etc. But = that's=20 not really how Gesture is used in Tapestry, since Gesture should = be used=20 when recognizing input (something the engine services do).</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>How about=20 "EncodingOfURLAndRequestParameters"? EncodedServiceRequest? =20 EncodedRequest? RequestEncoding? </FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>----<BR>Howard Lewis Ship<BR><A=20 href=3D"mailto:[email protected]">[email protected]</A><BR><A=20 href=3D"http://tapestry.sf.net">http://tapestry.sf.net</A><BR></FONT></DI= V></BODY></HTML> ------=_NextPart_000_0058_01C2AD7A.2E621370-- ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf