Re^2: Consistent naming for methods that return HTML::Template prepped data?

get_x() and set_x doesn't necessarily have to be db retrieval, etc. What if I am getting a listing of files on disk?

I think I should keep get_directory_list() doing a normal return of array ref to list of files for a directory- for development, for coding use. And I would still need get_directory_list_prepped()

Yes, your suggestion is golden in regards to db retrieval! Althought- it *could* cripple preformance for large datasets- right?

Often the data that will be fed to the template is not so simple- It may be a collection of data on disk, metadata in a db, something in relation with who is viewing the data.. etc. Real time things that change and need to be looked up at the moment.

Comment on Re^2: Consistent naming for methods that return HTML::Template prepped data?

Replies are listed 'Best First'.
Re^3: Consistent naming for methods that return HTML::Template prepped data? by jeffa (Bishop) on Oct 23, 2006 at 16:14 UTC
get_x() and set_x doesn't necessarily have to be db retrieval, etc. What if I am getting a listing of files on disk? Leave that up to the implementation of the class you are building. I think I should keep get_directory_list() doing a normal return of array ref to list of files for a directory- for development, for coding use. And I would still need get_directory_list_prepped() I would consider using one method, `get_directory_list()`, and pass a parameter in that specifies what kind of data structure to return. I might even consider using a Factory Pattern. Yes, your suggestion is golden in regards to db retrieval! Althought- it could* cripple preformance for large datasets- right?* Thanks, that's just advice i have picked up from hanging out here at the Monastery. As for large datasets ... anything that returns large datasets should be identified and handled accordingly. Sometimes you can even apply outside solutions to the problem, so don't think you have to always sacrifice development/maintenance effeciency for runtime efficiency. And as for data ... well, data is as data does. :) I have used AJAX in conjuction with Perl to handle "real time" lookups and it wasn't so bad after all. jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply]

Replies are listed 'Best First'.

Re^3: Consistent naming for methods that return HTML::Template prepped data?
by jeffa (Bishop) on Oct 23, 2006 at 16:14 UTC

get_x() and set_x doesn't necessarily have to be db retrieval, etc. What if I am getting a listing of files on disk?

Leave that up to the implementation of the class you are building.

I think I should keep get_directory_list() doing a normal return of array ref to list of files for a directory- for development, for coding use. And I would still need get_directory_list_prepped()

I would consider using one method, get_directory_list(), and pass a parameter in that specifies what kind of data structure to return. I might even consider using a Factory Pattern.

Yes, your suggestion is golden in regards to db retrieval! Althought- it *could* cripple preformance for large datasets- right?

Thanks, that's just advice i have picked up from hanging out here at the Monastery. As for large datasets ... anything that returns large datasets should be identified and handled accordingly. Sometimes you can even apply outside solutions to the problem, so don't think you have to always sacrifice development/maintenance effeciency for runtime efficiency. And as for data ... well, data is as data does. :) I have used AJAX in conjuction with Perl to handle "real time" lookups and it wasn't so bad after all.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

[reply]