-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This sounds good to me.

Josh

On Mon January 11 2010 2:00:47 pm Aaron Peeler wrote:
> I've started working on this issue to improve the block request processing
> and would  like some feedback.
>
> As part of this. I would like to clean up utils.pm by moving several
> block_request related routines from utils.pm to blockrequest.pm and would
> like to make sure there are not any issues with moving these routines.
>
> The routines and their descriptions are listed below in the format
> routine, description.
>
> process_block_time, calls utils::xmlrpc_call routine with specified method
> and args
>
> update_blockrequest_processing, Updates the processing flag in the
> blockRequest table
>
> update_blockTimes_processing, Updates the processed flag in blockTimes
> table
>
> delete_block_request, removes a blockrequest
>
> clear_blockTimes,  Removes blockTimes id from blockTimes table
>
> clear_blockComputers, Updates the processed flag in blockTimes table
>
>
> A quick scan shows these routines are only being called from
> blockrequest.pm, so there should be zero impact.
>
> Thanks,
> Aaron
>
> Aaron Peeler
> OIT Advanced Computing
> College of Engineering-NCSU
> 919.513.4571
> http://vcl.ncsu.edu

- -- 
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at www.keyserver.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iD8DBQFLTO81V/LQcNdtPQMRAhXbAJ9BLXS7ozEdgZ0L20VA9aZUWAaRJgCfWBlZ
SPRpnC/9kQZ/PQIu+WeNAqI=
=nDrJ
-----END PGP SIGNATURE-----

Reply via email to