like i said, i think that we have some friendly disagreement... > I'd say that displaying the rows in alternating colors > is a function of the presentation. > > But what order the rows are given is business logic, > and should be part of the business API. > > Ordering rows one way or another is something that > your application does -- it reports by the last name, > or invoice date, et cetera. And these are things that > should be expressed in the queries and maybe optimized > by the DBA. > > The real test case is this: > > OK, we're not using browsers any more. Users an can now > request a report as a PDF as an email attachment in any > supported order. Now how does the data get ordered?
i think that your phrase "the real test case is this:" is attempting to justify your decision. let me try to rephrase it a little bit... the real test case is this: what solution provides the most benefit for the end users of the system? as software developers we should not write software in a particular fashion just because there is a "rule" that says so. the software that we write is for users and because users want and need so many different things we have to be flexible about how we give it to them. there is nothing wrong with providing sort functionality on the server side because it fulfills a user need. there is also nothing wrong with providing sort functionality in a client application because it also fulfills a user need. when we generate a PDF report on the server, we use server side sorting of data. why do we do that? not because there is a rule that says all of the sorting must occur on the server but because that is the best way to fulfill our user's wants and needs. we have a wide array of tools at our disposal and not using them fully in order to satisfy our customers is kind of silly. rjsjr -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
