Juergen Donnerstag wrote:
I'm a little bit uncertain. I myself get sometimes confused with the
servlet classes while trying to understand the code. Than I hover over
the variable and check where it is imported from. From that point of
Web* would make sense.
On the other side what they actually handle are http requests. Or am I
wrong and they are able to handle different protocols as well. I can't
think of any currently, but lets say you use JMS to receive the
requests and to return the responses. Http* would be "wrong" than.
the protocol independent classes are Request, Response, RequestCycle and
Session
the protocol-specific subclasses are HttpRequest, HttpResponse... etc.
Web is really another, more abstract word for Http in this case.
Again, I'm a bit uncertain. My gut feeldings are: change to Web*
Juergen
On Mon, 07 Feb 2005 20:35:43 -0800, Jonathan Locke <[EMAIL PROTECTED]> wrote:
when there's something to be gained, i agree. like Session (which is
overloaded by hibernate).
i just feel like the Http* classes /aren't/ servlet classes. they're
abstractions and as such, i think
the name web is more familiar than http, which might get people thinking
the wrong things if
they look at code out of context... still, if other people agree that
the current names are best,
i'm willing to back off. i'd like to hear what eelco and juergen think...
Gili wrote:
Personally I prefer the original naming. I have always felt
that trying to avoid name conflicts even though the classes exist in
two different packages is a waste of time. I actually *prefer* having
wicket.util.List instead of some ambigious class name I am not used to.
That's what IDEs are for. They resolve the classes for you and I really
don't think it is such a big deal. I am much more interested in having
the resulting code be readable, containing familiar class names, than
have to learn all these new concepts. Just my 2 cents.
I know Netbeans has a great auto-import engine. I suspect
Eclipse does too. So why the hesitation to use familiar names?
Gili
On Mon, 07 Feb 2005 19:51:43 -0800, Jonathan Locke wrote:
i was thinking things would be more consistent and less confusing if we
didn't use the Http* names (because they conflict with servlet API class
names).
so i was thinking of renaming:
HttpRequest -> WebRequest
HttpRequestCycle -> WebRequestCycle
HttpReponse -> WebResponse
HttpSession -> WebSession
the mock objects would stay the same since they are implementing the
actual servlet API interfaces
this would have the benefit of matching the existing WebApplication
class and providing easy distinctions between the Web* Wicket
abstractions and the Http* servlet API stuff
any thoughts?
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
