well the key defines if CS should refresh when the M2 app is refreshed. But if say you have a hook to cause all submodules to refresh in one request, sounds like we would need a request key like hasRefreshed, so it only occurs one time


On Dec 20, 2006, at 8:23 AM, Tom Chiverton wrote:

On Tuesday 19 December 2006 00:30, Chris Scott wrote:
by default reload every time, but if you define a reload key (easily
set it to the same as the M2 one, or a different one) each app would
not always reload CS when it loads

Why wont this lead to dependancy hell, as you try and figure out which order 
the various keys must be refreshed in ?

-- 
Tom Chiverton
Helping to centrally benchmark unique systems

****************************************************

This email is sent for and on behalf of Halliwells LLP.

Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF.  A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society.

CONFIDENTIALITY

This email is intended only for the use of the addressee named above and may be confidential or legally privileged.  If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents.  If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008.

For more information about Halliwells LLP visit www.halliwells.com.



Reply via email to