collective / Products.TrackConflictErrors

0 stars 1 forks source link

Can we combine the report screen and the control panel screen? #3

Open sureshvv opened 10 years ago

sureshvv commented 10 years ago

Everything in one place

sureshvv commented 10 years ago

Just a checkbox for enabling/disabling tracking

abhi8812 commented 10 years ago

In ConflictTracker Report we have one button with name stop logging will stop the logging temporarly and later we can restart using StartLogging button

sureshvv commented 10 years ago

Yes. I saw that. I think a checkbox will be a better interface.

Do you agree with making the report part of the controlpanel screen itself?

sureshvv commented 10 years ago

Instead of Number of Plone Instances and Directory, make it 1 field - a list of log files. Log file naming convention has been (and may be) different at different locations and times,

Also validate the input by checking that the files exist.

sureshvv commented 10 years ago

How will this work when there are multiple zeo clients? will everything get multiplies n times>

sureshvv commented 10 years ago

How can we ensure that the same zeo client will handle the stop logging request as the one that started it? What happens if it goes to a different zeo client?

abhi8812 commented 10 years ago

Dear Sir, The following code will run by separate Thread python process so i think it does not matter which clients handle the request: def run(self): self.resume() patteren="conflict error" while True: with self .state: if self.paused: self.state.wait() # block until notified for item in self.files: for items in item: if patteren in items: self.results.append( items) else: item.seek(item.tell()) time.sleep(self.time_interval) because while loop will run infinite time. Thanks & Regards: Abhishek Sharma

On Mon, Oct 27, 2014 at 1:33 PM, sureshvv notifications@github.com wrote:

How can we ensure that the same zeo client will handle the stop logging request as the one that started it? What happens if it goes to a different zeo client?

— Reply to this email directly or view it on GitHub https://github.com/collective/Products.TrackConflictErrors/issues/3#issuecomment-60559768 .