Re: Application design

Thanks Patrice,

I have never done a queue based system (and also done very little in the way
of generating events, which leads me onto a new thread that I will ask in a
short while.).

Would you be able to do a quick mock up so that I can understand the
principle (or point me in the direction)?

Thanks.

--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available

"Patrice" <http://www.chez.com/scribe/> wrote in message
news:BE6B921E-0F83-43FE-9562-8658659E93CA@xxxxxxxxxxxxxxxx
Same as Peter, I meant I would add them a processing queue (this is the
word I omitted) or even queues (for example depending on priority) . In
addition to the pure technical difference between a file system watcher
and a queue, I feel it would allow to store some additional data that
could help in managing each entry.

It should be quite easy to do a mock up to simulate the base principle you
would use...

--
Patrice

"David" <david.colliver.NEWS@xxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de groupe de discussion : O1dGeBcOJHA.1744@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

Thanks Sloan, Peter and Patrice. Definately food for thought.

Patrice, can you expand on what you mean?


The system has to work with a plugin architecture and be scalable. For
example, it will also be database driven and I need to be able to use
different databases. This I can easily achieve by using a layered
approach, something I haven't mentioned yet though is that it has to be
able to work from a clustered perspective as well (such as a clustered DB
server or clustered web server etc.) However, I don't think that affects
this part of the structure.


--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available


"Patrice" <http://www.chez.com/scribe/> wrote in message
news:DD4305A1-614E-44FB-BA1B-59CC117C006D@xxxxxxxxxxxxxxxx
As files are submitted by using a web service I would add them to a
processing at this point rather than just using the file system. This
way you can add whatever you want to each entry (either priority,
chronological time, current status, and even try to reprocess in case of
a failure).

Similary it should be easier to use multiple threads if needed this
way...(i.e. basically you just share reading/setting the current
status).

--
Patrice

"David" <david.colliver.NEWS@xxxxxxxxxxxxxxxxxxxxxxx> a écrit dans le
message de groupe de discussion :
uJyGYbSOJHA.4372@xxxxxxxxxxxxxxxxxxxxxxx
Hi,

This question could be very subjective but I am after a way to design
this...

I am developing in C#, .NET 2.0

Basically, I have data coming in from a mobile phone. This is sending a
file to a webservice. The webservice will save the file to local disk
and also send / receive messages from the mobile phone. This part is
working fine, though wether I should have a multi-thread on this, I
don't know.


Once the file has been saved, I need to then work on it. The process
can become quite intensive. Also, each file can come from a different
customer and each customer will have a 'priority' preference, for
example, some files have to be acted upon immediately (due to them
being time critical) where others that are not so critical can wait.


My thoughts to handle this is a windows service with a filewatcher to
watch the webservice receiving folder. Then, depending on the file
(customer), react to it...

I guess I should be doing threading here (I have not really done any
threading before...) but I do have to bear in mind priority files.
Also, if there are for example, 3 files from one phone, they have to be
handled chronologically.

We could be talking many thousands of files per day that need to be
handled (both for the webservice and windows service). Also, there
could be varying outputs, for example, some customers may just want a
raw processed file (XML), others may want an image while others may
want a PDF. Also, any / all of these could be selected.

Finally, the file can be delivered either back to the phone, via email,
via FTP, HTTP to another web server or any other common communications
technology. (Again, any / all options could be selected.)

I also have to make the application work on mulitple servers, though
that probably won't be such an issue unless I have a common fileserver
to store the incoming files and the filewatcher service on two servers
both attempt to collect the same file.

Ideas on how I should approach this would be very much appreciated.


--
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available







.

Relevant Pages

  • Re: Application design
    ... In particular depending on your architecture using MSMQ could help... ... I have never done a queue based system (and also done very little in the ... DB server or clustered web server etc.) However, ... customer and each customer will have a 'priority' preference, ...
    (microsoft.public.dotnet.framework)
  • Re: Application design
    ... I meant I would add them a processing queue (this is the word ... I omitted) or even queues (for example depending on priority). ... server or clustered web server etc.) However, ... customer and each customer will have a 'priority' preference, ...
    (microsoft.public.dotnet.framework)
  • departure process in a queue
    ... there are free server, the customer will occupy one server. ... no server is avaiable and the queue is full, ... if the service time follows other distribution, ...
    (sci.math)
  • departure process in a queue
    ... there are free server, the customer will occupy one server. ... no server is avaiable and the queue is full, ... if the service time follows other distribution, ...
    (sci.stat.edu)
  • Re: synchronizations of threads
    ... To answer your immediate question, it's not the lock using workLock that's superfluous, it's the lock using workQueue. ... As has been discussed elsewhere, including in Jon Skeet's web article on threading, using a privately allocated instance of Object for a lock is preferable to using the object that actually needs the synchronized access, because doing so ensures that only that particular code is locking on that particular object. ... I am surprised to see the non-generic Queue class being used, but more significantly the use of the "stop" variable to signal a shutdown rather than just communicating through the queue, which leads to the two-second timeout, another questionable design choice, and the fact that the workLock lock is held during the entire execution of the worker delegate, these are all bad problems IMHO. ...
    (microsoft.public.dotnet.languages.csharp)