Well time will tell. We'll know for sure once the prototyping is done. Once it's done I'll post it here as an article so I can get more feedback. Thanks for your input. If it's not broken, fix it until it is

zephaneas wrote: From what I can see that's the whole point of WebSockets, and SignalR which is built on it We either have a nomenclature issue or you are mistaken about what websockets do (I know nothing about the second.) Communication involves two parts 1. Establishing the connection 2. Sending messages. In normal communications, like web traffic a client (from any computer, any application) attempts to 'connect' to the server (any computer and server applications.) Websockets allow a client to create a connection to a server and then facilitate message handling (2 in the above) between the client and the server. A real callback requires a reverse of that connection protocol in that the server would then need to do 1 by attempting to connect to the original client. Websockets do not do that. Some reasons for clients not doing real callbacks. 1. The server cannot in fact connect to the client. Although a client might have a route to a server the server is not likely to have a route to the client. Nor even know how to connect to the client. This is much, must more likely to be true on the internet. 2. Servers are intended to be static resources. Clients are temporary. Thus even if a server attempted a callback the client might no longer be there. 3. Establishing connections can be a resource intensive process as is handling connections. Asking a server to do both, when a client is likely connecting to the server often in the first place is a pointless waste of resources. Not to mention adding complexity to the system.

zephaneas wrote: Any reason not to upgrade? None. Mobile Apps - Sound Meter | Color Analyzer | SMBC | Football Doodles

http://www-03.ibm.com/software/products/en/ratidoorng[^] Do not escape reality : improve reality !

zephaneas wrote: What are they asking here? I don't understand either. Maybe they meant "unit test" rather than "unit"? Or maybe they meant you were re-using code from an MVC project in your WPF project. There is no harm is asking them to explain what they mean.

I'm pretty sure it uses a shell extension to implement the Drop Box folder. Shell Extensions are no laughing matter because they can be complicated. The difficult we do right away... ...the impossible takes slightly longer.

The comedian Gallagher did the whole lowest common denominator bit about hots dogs and buns in the mid 1970's.

Your second example is not the correct way to use async. You should avoid async void wherever possible: Avoid async void methods[^] You might also get better performance if you use an asynchronous Stream to read the file. Try this: static void Main(string[] args) { Console.WriteLine("Task 1 started"); Task task = ProcessDataAsync(); task.Wait(); Console.WriteLine("The READ task was started"); Console.ReadLine(); } static async Task ProcessDataAsync() { Task task = HandleFileAsync(sampleFile); Console.WriteLine("Getting ready to read the file."); int x = await task; Console.WriteLine("Count: " + x); } static async Task HandleFileAsync(string file) { Console.WriteLine("HandleFile enter"); int count = 0; using (Stream stream = new FileStream(path, FileMode.Open, FileAccess.Read, FileShare.Read, 4096, FileOptions.Asynchronous)) using (StreamReader reader = new StreamReader(stream)) { Console.WriteLine("Reading the file."); string v = await reader.ReadToEndAsync(); count += v.Length; } Console.WriteLine("HandleFile exit"); return count; } "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Would assume that some part of the programming would involve real-time acquisition / monitoring of data, not missing data for even a single time instant. In essence, aspects of multi-threaded programming, concurrency, etc.

So you've been working for 2 years on this project. Was the project a coding project or was it a monthly maintenance plan project? If it was a coding project, have you completely satisfied your end of the contract agreement? If you haven't yet finished the project, certainly there must be some areas in the project that still need your attention. Or is that all out of the way? If it was a service you were performing for the client and he didn't pay, in the U.S., we have what is called 'Theft of Services', but you'll have to prove that your client intended to use your service without the intention of paying for it. But, then again, you're dealing with international laws. If you've completed the project, how many payments was he outstanding? There should be no reason for you to act out of character. In the U.S., it's normal for businesses to take up to 90 days to pay. You can still write it off as a business loss from your taxes. Although, you'll have to show a good faith effort in trying to collect, (i.e., send emails to the client requesting payment and stating your intentions for a reasonable period of time). Even for large amounts of outstanding balances owed to us, it's sometimes better to cut your losses and run. Figuring that the amount of time, money and thought you spend trying to collect, you could put to better use cultivating another better paying client. And, you'll write all this new learned experience into your contract so that you can have some control the next time this happens, and not have to commit a criminal act. Big rocks and little rocks and sand. Happy coding, hope you get paid!

oooohhhh...Sig 220! Purty thang! I settled for a Glock 30 because of price (I paid a little less than half the MSRP of the 220) and the ten round double stack. It's ugly as a brick, but works fine, should last long time. cat fud heer

Excellent advice, Walt. If I was Company A, paying him for a 40 hour week, I'd expect his full attention during my normal work week. If he wants to have a second job, it had better be handled after hours, and he'd better not show up in the morning sleepy. If company B has a problem with that, assuming that company A was already contracted, they need to adjust their expectations from a part-timer, or compensate enough to give him a reason to default on the company A contract. That can be a lot more than face value, since abandoning company A will have long term effects. People do talk, and word will get around if he defaults on his first obligation. The second employer had better pay enough to retire on... :-D Will Rogers never met me.

Oh don't worry, I often think the same about that as well. ;P

Make sure you're running in debug mode... if you click on "Continue" and it doesn't do anything, that's usually an indication that you're in release mode and your executable hasn't been build with debug information.

John Simmons / outlaw programmer wrote: I'm not a hand wringer That's for sure. :) That said, I fail to see the reason for people's angst over the new Start screen. If you spend your time at the desktop, you're really not going to notice it much -- again, only when you go to start an app that you haven't pinned to the taskbar. I realized that I'm officially a fanboi at this point, but I'm also a desktop user, for app development at least, and am satisfied (to say the least) with Windows 8 on my non-touch, 4-year-old, notebook.

zephaneas wrote: A) It must contain at least one vowel. So, a password of a is enough to satisfy the criteria. As others have said, he needs to be educated as to best practices (e.g. use of symbols, minimum length, etc). To answer the question though - I wouldn't use RegEx for something like this. You may get a working regular expression, but it will be tied to these requirements. If the criteria expands, you'll have to revisit the regex, and you may find that the solution is no longer valid. A fairly elegant solution would be to use the Visitor Pattern[^]. With this, you can add new rules without affecting the underlying logic, simply by adding new visitors. *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington "Mind bleach! Send me mind bleach!" - Nagy Vilmos CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier