Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed2.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'example:': 0.03; 'algorithm': 0.03; 'modified': 0.05; 'filename': 0.07; 'key.': 0.07; 'table.': 0.07; 'python': 0.09; '(without': 0.09; 'added.': 0.09; 'filenames,': 0.09; 'happen.': 0.09; 'identifier': 0.09; 'identifier,': 0.09; 'mess': 0.09; 'template': 0.11; 'files.': 0.13; 'file,': 0.15; 'value.': 0.15; '(eg.': 0.16; 'altered,': 0.16; "file's": 0.16; 'modified.': 0.16; 'renamed': 0.16; 'retains': 0.16; 'rewriting': 0.16; 'somehow,': 0.16; 'sources,': 0.16; 'later': 0.16; 'wrote:': 0.17; 'mathematical': 0.17; 'mechanism': 0.17; 'solution.': 0.18; 'embedding': 0.22; 'latter': 0.22; 'programming': 0.23; 'thus': 0.24; 'external': 0.24; 'script': 0.24; 'header:In-Reply-To:1': 0.25; 'header:User- Agent:1': 0.26; '(e.g.': 0.27; 'am,': 0.27; 'checking': 0.27; 'embedded': 0.27; 'separate': 0.27; 'hash': 0.29; 'key,': 0.29; 'nice!': 0.29; 'case,': 0.29; 'no,': 0.29; '"the': 0.29; 'figure': 0.30; 'code': 0.31; 'gets': 0.32; 'problem.': 0.32; 'file': 0.32; 'not.': 0.32; 'sources': 0.32; 'could': 0.32; 'directory,': 0.33; 'zero': 0.33; 'to:addr:python-list': 0.33; 'another': 0.33; '(1)': 0.34; 'updated': 0.34; 'list': 0.35; 'desirable': 0.35; 'path': 0.35; 'problem,': 0.35; 'replaced': 0.35; 'requiring': 0.35; 'so,': 0.35; "won't": 0.35; 'there': 0.35; 'created': 0.36; 'but': 0.36; "didn't": 0.36; 'enough': 0.36; 'ones': 0.37; 'subject:: ': 0.38; 'store': 0.38; 'files': 0.38; 'mean': 0.38; 'some': 0.38; 'things': 0.38; 'page': 0.38; 'instead': 0.39; 'to:addr:python.org': 0.39; 'received:192': 0.39; 'list,': 0.39; 'received:192.168': 0.40; 'end': 0.40; 'your': 0.60; 'real': 0.61; 'information': 0.63; 'therefore': 0.65; 'subject: & ': 0.67; '8bit%:100': 0.70; '8bit%:92': 0.70; 'received:74.208': 0.71; 'sounds': 0.71; '2013': 0.84; 'actions,': 0.84; 'altered)': 0.84; 'choices:': 0.84; 'situations,': 0.84; 'updated,': 0.84; 'same,': 0.91; 'angel': 0.93 Date: Sat, 19 Jan 2013 04:00:15 -0500 From: Dave Angel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Uniquely identifying each & every html template References: <8deb6f5d-ff10-4b36-bdd6-36f9eed58e1e@googlegroups.com> <5dd4babd-716d-4542-ad36-e6a841b73ec3@googlegroups.com> In-Reply-To: <5dd4babd-716d-4542-ad36-e6a841b73ec3@googlegroups.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:/Jp8oYurVW9ZeC6yX+b6G3M4Fq7GFzi+wtAtW6SzwNg Y8W3TimUbMtuU8PgfenP8RwmROmc3SF63a4/WqXuYazaxlrD5d 4aVakv25sqNUXZ8C/LHjpqO+Rf4YinCX6/C68vUfVYetIaAvzc 8pPJsSw6Xu/JY1q6Fmc1MeR5U1cteIxUsN9cQLEffD7h/eXDK7 XLvrr0dLtwylzGkMZycwFWkHIs7tRvriNYq4wHMS7uLSjkTdXK ebSPiNEGzEWyPfZsK+riO9TjbazWk6WipOiVF1oiXn1FdHfPza l9xzByvaHvLeo9t9Dox3/U9YDuvbjb5gsdSlIIJzc9R4bzsfQ= = X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 66 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1358586035 news.xs4all.nl 6940 [2001:888:2000:d::a6]:56651 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:37076 On 01/19/2013 03:39 AM, Ferrous Cranus wrote: > Τη Σάββατο, 19 Ιανουαρίου 2013 12:09:28 π.μ. UTC+2, ο χρήστης Dave Angel έγραψε: > >> I don't understand the problem. A trivial Python script could scan >> >> through all the files in the directory, checking which ones are missing >> >> the identifier, and rewriting the file with the identifier added. > >> >> So, since you didn't come to that conclusion, there must be some other >> >> reason you don't want to edit the files. Is it that the real sources >> >> are elsewhere (e.g. Dreamweaver), and whenever one recompiles those >> >> sources, these files get replaced (without identifiers)? > > Exactly. Files get modified/updates thus the embedded identifier will be missing each time. So, relying on embedding code to html template content is not practical. > > >> If that's the case, then I figure you have about 3 choices: >> 1) use the file path as your key, instead of requiring a number > > No, i cannot, because it would mess things at a later time on when i for example: > > 1. mv name.html othername.html (document's filename altered) > 2. mv name.html /subfolder/name.html (document's filepath altered) > > Hence, new database counters will be created for each of the above actions, therefore i will be having 2 counters for the same file, and the latter one will start from a zero value. > > Pros: If the file's contents gets updated, that won't affect the counter. > Cons: If filepath is altered, then duplicity will happen. > > >> 2) use a hash of the page (eg. md5) as your key. of course this could >> mean that you get a new value whenever the page is updated. That's good >> in many situations, but you don't give enough information to know if >> that's desirable for you or not. > > That sounds nice! A hash is a mathematical algorithm that produce a unique number after analyzing each file's contents? But then again what if the html templated gets updated? That update action will create a new hash for the file, hence another counter will be created for the same file, same end result as (1) solution. > > Pros: If filepath is altered, that won't affect the counter. > Cons: If file's contents gets updated the, then duplicity will happen. > > >> 3) Keep an external list of filenames, and their associated id numbers. >> The database would be a good place to store such a list, in a separate table. > > I did not understand that solution. > > > We need to find a way so even IF: > > (filepath gets modified && file content's gets modified) simultaneously the counter will STILL retains it's value. > You don't yet have a programming problem, you have a specification problem. Somehow, you want a file to be considered "the same" even when it's moved, renamed and/or modified. So all files are the same, and you only need one id. Don't pick a mechanism until you have an self-consistent spec. -- DaveA