Multi-thread, read/write to single file.

Multi-thread read/write to a single file.

I have two processing threads, thread A and thread B; and I called my
queue as Q.

Thread A will feed data into Q by user input, the timing is random.
Thread B will read data from Q to process; this processing will
communicate with a website.

I think the best Q architecture is ring buffer as large as possible.
However, my idea is to create a textbox.

The problem is the two threads might read/write to Q at the same time.
So, what I need to do is to suspend thread whenever user is submitting
data to Q?

How about when thread B is deleting data (because the data was
processed), I might need to suspend thread A, but thread A is user
interface, there should never a latency.

So, my idea is, UI should separate from processing thread.

Please give me any of your ideas.

Thanks!

Best regards,
Boki.

It sounds like you are saying you have a class A that directly manipulates
the queue, as does class B, rather than both interacting through methods on a
class Q. I believe A and B should not care about the workings of Q. A
should simply call Add(xyz), while B should call Subtract() that returns the
next item (and pulls the data of the queue internally).

"Boki" wrote:

Multi-thread read/write to a single file.

I have two processing threads, thread A and thread B; and I called my
queue as Q.

Thread A will feed data into Q by user input, the timing is random.
Thread B will read data from Q to process; this processing will
communicate with a website.

I think the best Q architecture is ring buffer as large as possible.
However, my idea is to create a textbox.

The problem is the two threads might read/write to Q at the same time.
So, what I need to do is to suspend thread whenever user is submitting
data to Q?

How about when thread B is deleting data (because the data was
processed), I might need to suspend thread A, but thread A is user
interface, there should never a latency.

So, my idea is, UI should separate from processing thread.

Please give me any of your ideas.

Thanks!

Best regards,
Boki.

There are a variety of ways to do this. If one of the threads is the
main GUI thread, then you can use Control.Invoke( ) or
Control.BeginIn voke() from the other thread to add things to queue.

On Mon, 09 Jul 2007 20:01:42 -0700, Peter Duniho

<NpOeStPe...@nn owslpianmk.comw rote:

There are a variety of ways to do this. If one of the threads is the
main GUI thread, then you can use Control.Invoke( ) or
Control.BeginIn voke() from the other thread to add things to queue.

Addendum:

Of course, if the other thread is the one that removes things rather than
add things, then that would work fine too. The key is synchronizing
access by ensuring that all access happens on the same thread.

On Jul 10, 10:50 am, ModelBuilder
<ModelBuil...@d iscussions.micr osoft.comwrote:

It sounds like you are saying you have a class A that directly manipulates
the queue, as does class B, rather than both interacting through methods on a
class Q. I believe A and B should not care about the workings of Q. A
should simply call Add(xyz), while B should call Subtract() that returns the
next item (and pulls the data of the queue internally).

"Boki" wrote:

Multi-thread read/write to a single file.

I have two processing threads, thread A and thread B; and I called my
queue as Q.

Thread A will feed data into Q by user input, the timing is random.
Thread B will read data from Q to process; this processing will
communicate with a website.

I think the best Q architecture is ring buffer as large as possible.
However, my idea is to create a textbox.

The problem is the two threads might read/write to Q at the same time.
So, what I need to do is to suspend thread whenever user is submitting
data to Q?

How about when thread B is deleting data (because the data was
processed), I might need to suspend thread A, but thread A is user
interface, there should never a latency.

So, my idea is, UI should separate from processing thread.

Please give me any of your ideas.

Thanks!

Best regards,
Boki.

Ya, I just finished the code, and the result works well.

It sounds great, but I am confused, we don't need to consider the
conflict on reading/writing to a same file at the same time ?

Because I temporally test with a textbox ( however, it works well, but
I feel there is a automatically delay by windows OS, not my code
controlling ).

Speaking to the architecture, finally, I will implement to a real text
file on the storage, I think in the future, more threads ( maybe more
execution files ) are reading/writing to same file at the same time.

I think I might need to consider this issue (?)

Best regards,
Boki.

Multi-thread read/write to a single file.

I have two processing threads, thread A and thread B; and I called my
queue as Q.

I think the best Q architecture is ring buffer as large as possible.

However, my idea is to create a textbox.

The problem is the two threads might read/write to Q at the same time.
So, what I need to do is to suspend thread whenever user is submitting
data to Q?

How about when thread B is deleting data (because the data was
processed), I might need to suspend thread A, but thread A is user
interface, there should never a latency.

Hi,

"Boki" <bokit...@ms21. hinet.netwrote in message

news:11******** *************@x 35g2000prf.goog legroups.com...

Multi-thread read/write to a single file.

I have two processing threads, thread A and thread B; and I called my
queue as Q.

U mean that you are ACTUALLY using a queue right?
If that is so, use a synced queue (by using Queue.Synchroni zed(
yourQueue) ).
After that all the operations will be thread safe.

I think the best Q architecture is ring buffer as large as possible.

Humm, what about using your synced Queue?

However, my idea is to create a textbox.

You lost me here, what a textbox has to do with this?

The problem is the two threads might read/write to Q at the same time.
So, what I need to do is to suspend thread whenever user is submitting
data to Q?

If you use a sync'ed Queue the framework will take care of that for you.

How about when thread B is deleting data (because the data was
processed), I might need to suspend thread A, but thread A is user
interface, there should never a latency.

If you use a sync'ed Queue you can access it from both threads without any
problem.