|
That seems reasonable. I don't know anything about reading messages from a mail server, but...
Each thread can read and parse one message and report back the result to be written. Whether or not the thread also downloads the message I don't know, but that should be doable.
So you can have a class that distributes work to a bunch of threads.
The process on the thread performs the work and reports back when finished.
For writing, you can have an event handler that locks a stream when it writes.
|
|
|
|
|
This is an example of the first section of the mail that I'm working with...
+OK 670581 octets
Return-Path: <email address>
Received: from hrndva-omtalb.email host([ip address])
by hrndva-imta01.email hostwith ESMTP
id <20100324163246244.LLFZ11363@hrndva-imta01.email host>
for <email it's going to>; Wed, 24 Mar 2010 16:32:46 +0000
Return-Path: <email address>
X-Authority-Analysis: v=1.0 c=1 a=Y--C8wIrtp4A:10 a=ed-Ggqp32-PxgnFQ28IA:9 a=gFYqYUHr3cvJf5tUtWv3jj12YwYA:4 a=wPNLvfGTeEIA:10 a=SSmOFEACAAAA:8 a=Xz8RjLcVAAAA:8 a=bvyAQD6M8USi_luE8VwA:9 a=zkXRgtjM-mmOsYMX5XAA:7 a=lSBj04H3UYGbvfZ5gLKUj7ga3v4A:4 a=TQY7aazGoy4vupPYzM8A:9 a=A9QQSRYdmLSsclXicRDPQfuie2oA:4 a=IKIoO-ieCDEA:10 a=l42U5Vqe35IA:10 a=OU-3oeRcviPOZ7V7:21 a=r3OCwUNA-PGXxiAt:21
X-Cloudmark-Score: 0
X-Originating-IP: IP Address
Received: from [IP Address] ([IP Address] helo=computer it's from (I think))
by hrndva-oedge02.email host (envelope-from <email address>)
(ecelerity 2.2.2.39 r()) with ESMTP
id 8E/A4-28072-8AE3AAB4; Wed, 24 Mar 2010 16:32:45 +0000
Received: from 127.0.0.1 (AVG SMTP 8.5.437 [271.1.1/2767]); Wed, 24 Mar 2010 12:31:41 -0500
Message-ID: <006301cacb77$ddf18460$ae02a8c0@pc it's from>
From: "Name" <emailaddress>
To: "person it's going to" <their email>
Subject: kinda obvious but using this data
Date: Wed, 24 Mar 2010 12:31:41 -0500
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_005F_01CACB4D.F4FC82B0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1983
Disposition-Notification-To: "Person from" <email address>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1983
There is a lot more after that but should give you an idea... hope I replaced all the stuff I should have 
|
|
|
|
|
Ok so to speed up that section you are suggesting to create a class that passes work to lets say 4 background workers? That sounds really good, but I've never done anything like that and how would I then return that info back to the Form? With a return? I would also loose my updates on the progressBar would I not?
Ok my brain is really starting to hurt now, thankfully I've only got 10 min left in my day right now... will have to get back to this tomorrow!
Thank you all for everything thus far...
|
|
|
|
|
MacRaider4 wrote: return that info back to the Form
Well, I question the use of a form at all; I'd use a Windows Service, but that's just me. You can have a Service that pulls the data into the database and then the form pulls it (already fluffed and folded) from there.
Or you could use an event.
|
|
|
|
|
I'll have to look up services as I've never done anything with that before. Though I will say doing this project has made me a better C# programmer, at this rate in another year I'll be answering some of these questions for other people.
Some one else mentioned just doing this all in one pass, now that I'm looking back at my code I think that is a very good idea. Is this something I could do with the service or event?
I could then do my initial pass to get the number, then have a couple workers work on the list storing the data in arrays. Once those are done combine the arrays or better yet just have the arrays loaded stright into the database which should take no time at all even with checking to make sure that message isn't already there?
|
|
|
|
|
MacRaider4 wrote: have the arrays loaded stright into the database
Right. The Service would periodically (once a minute?) query the email server for messages, if there are some, get them, process them, and stick the results in the database. You could still use a thread to process each message in necessary.
Depending on your needs, you could then have the same Service host a WCF Web Service that your client application can use to get the data. 
|
|
|
|
|
That was my original intent once I got it working, just didn't know about the service part.
So let me see if I have this right now:
1. Log into the server and get the number of messages
2. Decide if I need to use a bgw and how many
3. Do the work with no or a couple workers:
a. have the worker/s log in with the number of account/s each is processing
b. process the "entire" message all at once and store in an array
4. Update the database
5. Have the form check fo updates?
Do this sound about right?
|
|
|
|
|
Yeah, basically. But remember that I'm not familiar with reading messages from an email server, so I don't understand the "a. have the worker/s log in with the number of account/s each is processing" part.
I would have a worker read a message, process it, and stick it in the database; then maybe get another.
Or read all the available messages and pass them to the workers.
There are many ways to skin this cat.
|
|
|
|
|
public Form1()
{
InitializeComponent();
InitializeBackgroundWorker();
InitializeBackgroundWorker2();
InitializeBackgroundWorker3();
btnGetMessageInfo.Enabled = false;
btnCancelConnection.Enabled = false;
}
private void InitializeBackgroundWorker()
{
backgroundWorker1.DoWork += new DoWorkEventHandler(backgroundWorker1_DoWork);
backgroundWorker1.RunWorkerCompleted += new RunWorkerCompletedEventHandler(backgroundWorker1_RunWorkerCompleted);
backgroundWorker1.ProgressChanged += new ProgressChangedEventHandler(backgroundWorker3_ProgressChanged);
}
private void InitializeBackgroundWorker2()
{
backgroundWorker2.DoWork += new DoWorkEventHandler(backgroundWorker2_DoWork);
backgroundWorker2.RunWorkerCompleted += new RunWorkerCompletedEventHandler(backgroundWorker2_RunWorkerCompleted);
backgroundWorker2.ProgressChanged += new ProgressChangedEventHandler(backgroundWorker2_ProgressChanged);
}
private void InitializeBackgroundWorker3()
{
backgroundWorker3.DoWork += new DoWorkEventHandler(backgroundWorker3_DoWork);
backgroundWorker3.RunWorkerCompleted += new RunWorkerCompletedEventHandler(backgroundWorker3_RunWorkerCompleted);
backgroundWorker3.ProgressChanged += new ProgressChangedEventHandler(backgroundWorker3_ProgressChanged);
}
So what I have now is when you click on the connect button (first thing you can do), it logs into the server and gets the total number and size of each message. And stores that in a global variable and displays some info on the form.
Then it figures out how many workers to use (based on number of messages)and assigns start and end values for each worker.
I'm now in the process of writing the work for the workers (focusing on 1 and 2 since only those work).
It's moving along, though slowly.
modified on Friday, February 11, 2011 1:33 PM
|
|
|
|
|
This is my first foray into real data binding in C# and .NET so forgive me if it's a stupid question. I have consulted MSDN and a number of CP articles but still cannot quite get my head round it.
I have a SortedList of objects (of my own Class) which I can successfully bind to my DataGridView so all the correct details are visible. I have also enabled "user can delete rows" on the DataGridView. However, when I delete some rows, the data is not removed from the datasource (the SortedList) as I thought it would be. I presume I have to add some other property, or implement some interface method in my class to make this happen.
Any suggestions?
I must get a clever new signature for 2011.
|
|
|
|
|
|
I don't quite see how that fits (the MSDN documentation on this subject really sucks). I have a SortedList bound to a DataGridView and I want the element(s) of the SortedList to be deleted when the user deletes the related row in the DataGridView. So where do I implement INotifyCollectionChanged? Or are you saying that I should provide my own collection class as the BindingSource?
I must get a clever new signature for 2011.
|
|
|
|
|
Richard MacCutchan wrote: Or are you saying that I should provide my own collection class as the BindingSource?
Yup. I'm usually using an ObservableCollection as it already has this functionality, not a SortedCollection. To quote the site;
"However, to set up dynamic bindings so that insertions or deletions in the collection update the UI automatically, the collection must implement the INotifyCollectionChanged interface. This interface exposes the CollectionChanged event that must be raised whenever the underlying collection changes."
I are Troll 
|
|
|
|
|
That all sounds fine, and I just found an article which covers this subject in some detail. However, my issue is that I want to be notified when the content of the DataGrid changes (user deletes a row) so I can update the contents of the data source (i.e. the collection). Both of the aforementioned features seem to be about notifying the UI when the underlying collection changes, but in my case the collection will not change on its own.
I must get a clever new signature for 2011.
|
|
|
|
|
Richard MacCutchan wrote: my issue is that I want to be notified when the content of the DataGrid changes (user deletes a row) so I can update the contents of the data source (i.e. the collection).
You were talking about a DataGridView earlier. The DataGrid has a RowDeleting[^] event, the DataGridView has a OnRowsRemoved[^].
Just dropped a grid on a form, and printed the count of the DGV-rows in that event. It does not alter the collection, only the rows in the DGV itself. ..dunno why, but something tells me that this event is probably not being raised in your project 
Richard MacCutchan wrote: Both of the aforementioned features seem to be about notifying the UI when the underlying collection changes
Yes, a biased mind
I are Troll
|
|
|
|
|
Eddy Vluggen wrote: You were talking about a DataGridView earlier.
I've been talking about it throughout this thread; indeed it is part of my subject line.
Eddy Vluggen wrote: something tells me that this event is probably not being raised in your project
Which is the entire issue I am struggling with. I delete some rows in the DataGridView but nothing changes in my data source (the SortedList). I thought data binding was there to solve problems, not to create them!
To recap: I have a SortedList bound to a DataGridView. When I delete a row from the DataGridView I expect the corresponding entry to be removed from the SortedList but I cannot find any examples or documentation to help explain why it doesn't happen. I'm somewhat surprised that no-one has come across this problem before.
I must get a clever new signature for 2011.
|
|
|
|
|
Richard,
Can you show the code that binds your SortedList to the DGV?
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Henry, the following is the method that sets up the DGV.
private void ShowVolunteers(SortedList<string, Volunteer> vols)
{
volList = vols.Values.ToList();
bindingSource.DataSource = volList;
volunteerGrid.DataSource = bindingSource;
volunteerGrid.DataBindings.DefaultDataSourceUpdateMode = DataSourceUpdateMode.OnPropertyChanged;
volunteerGrid.AutoGenerateColumns = true;
volunteerGrid.Focus();
}
The Volunteer class contains three string values which show up fine in the DGV. I tried adding the INotifyPropertyChanged interface to my Volunteer class (as suggested by Eddy) but it never gets called, since the actual objects do not get changed. The only 'changes' I want to allow is for the user to delete some rows from the DGV, and the data source to be updated automatically.
To be honest, I would not spend too much time on this as I have a work around, which is to use the DGV rows that remain to get the final results I need. However, if you can spot an obvious fix I would certainly be interested in knowing about it.
I must get a clever new signature for 2011.
|
|
|
|
|
I just wanted confirmation of how you were binding before I made my suggestion in order to prevent my usual faux pas.
You need to change the type of your volList to BindingList<Volunteer>
Then in your ShowVolunteers()
volList = new BindingList<Volunteer>(vols.Values.ToList());
*****NOTE****
This will propagate the deletion only as far as the bindingSource NOT to vols. To make this useful you will need to rebuild vols from bindingSource.List at an appropriate point.
Hope this helps. 
Henry Minute
Do not read medical books! You could die of a misprint. - Mark Twain
Girl: (staring) "Why do you need an icy cucumber?"
“I want to report a fraud. The government is lying to us all.”
I wouldn't let CG touch my Abacus!
When you're wrestling a gorilla, you don't stop when you're tired, you stop when the gorilla is.
|
|
|
|
|
Thanks, I'll give it a try and let you know.
I must get a clever new signature for 2011.
|
|
|
|
|
Thanks Henry, it works perfectly.
I must get a clever new signature for 2011.
|
|
|
|
|
In DoWork() function the thread is different from the main thread and Thread.CurrentThread.CurrentCulture is default one similar to Application.CurrentCulture
Is it possible to change worker culture to UI culture without passing it in arguments?
Чесноков
|
|
|
|
|
Why not use CultureInfo.CurrentUICulture?
|
|
|
|
|
That is the property returning current thread culture settings that is UI thread.
Чесноков
|
|
|
|
|
A new thread receives culture/UI culture from the Windows system - in my opinion that's a bug (but Microsoft may see that differently). I use to set the UI culture with a value from the .exe.config file - that can also be applied in a newly started thread. Otherwise, have a (static) member in some class/object you can access from the background worker.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
