Application design

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
    ... As files are submitted by using a web service I would add them to a ... I have data coming in from a mobile phone. ... file to a webservice. ... each file can come from a different customer ...
    (microsoft.public.dotnet.framework)
  • Re: Application design
    ... clustered web server etc.) However, I don't think that affects this part of ... I have data coming in from a mobile phone. ... file to a webservice. ... customer and each customer will have a 'priority' preference, ...
    (microsoft.public.dotnet.framework)
  • Re: Application design
    ... and expose it as a WebService. ... each file can come from a different customer ... My thoughts to handle this is a windows service with a filewatcher to ... the incoming files and the filewatcher service on two servers both attempt ...
    (microsoft.public.dotnet.framework)
  • Re: best practices on the creation of webmethods
    ... trips to the webservice. ... Find Customer ID based on Emailaddress ... > normally no other company will use our web service (we create the client ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: SCREWFIX - unsolicited TEXT messages
    ... Only a Pimp or reverse SMS seller would claim that, ... ad-hoc services on your mobile phone is useful. ... Letting the customer opt in is the only solution, ... The problem is that the system is already meant to be opt-in for each ...
    (uk.telecom.mobile)