conceptual

I have been fighting with multi threading for few days. I dont understand what are different ways of multithreading . I have read little bit about backgroundWorker , little bit about creating an object of thread. Yesterday I saw in delegate example to implement multithreading by calling BeginInvoke . I dont understand are these different ways of multithreading or are same working on same background class. Please help me in making it clear to me. I like this explanations very much. Maybe they help you, too. And then, there is this article by Jon Skeet, too. any thread without a GUI is a

Is it a bad practice when writing a RESTful API to use custom HTTP response codes like: 417 - Password not provided 418 - Database error I see there is a list of standard HTTP response codes . However, from looking at Twitter's API , it appears Twitter tries to return standard HTTP response codes when available but their own error codes when they cannot align the error with a standard HTTP response (correct me if I am wrong). What is the best practice for response codes (especially for errors) while creating a RESTful API? Any comments on the practice which Twitter chose to use? Yes, yes it is

Does anyone have a real world example outside of python's file object implementation of an __enter__ and __exit__ use case? Preferably your own, since what I'm trying to achieve is a better way to conceptualize the cases where it would be used. I've already read this . And, here's a link to the python documentation. There are many uses. Just in the standard library we have: sqlite3 ; using the connection as a context manager translates to committing or aborting the transaction. unittest ; using assertRaises as a context manager lets you assert an exception is raised, then test aspects of the

So, I had an argument with my professor earlier defending that NULL is not a pointer, but he kept on insisting that it is because there is such a thing as NULL pointer. So, here I am now a little bit confused if NULL is really a pointer or not I already tried search over the internet but couldn't find any answer, so my last resort is here In C, NULL is a macro that expands to a null pointer constant. 7.19p3 The macros are NULL which expands to an implementation-defined null pointer constant; ... A null pointer constant is an integer constant expression with the value 0 ( e.g., 0 , 1-1 , 42*0LL

Having passed a series of Edward Tanguay 's questions refractoring the usage of MVVM for WPF app which can be found in Linked sidebar of his Fat Models, skinny ViewModels and dumb Views, the best MVVM approach? , I am a little confused by his final WPF application in Big smart ViewModels, dumb Views, and any model, the best MVVM approach? Its M (Model) is Customer class : //model public class Customer { public string FirstName { get; set; } public string LastName { get; set; } public DateTime TimeOfMostRecentActivity { get; set; } public static Customer GetCurrentCustomer() { return new

I saw a code example that creates a method Window_Loaded() which is called by XAML's "Window Loaded" event: <Window x:Class="TestModuleLoader.Window1" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Title="Window1" Height="300" Width="300" Loaded="Window_Loaded"> <Grid> ... </Grid> </Window> But in the code behind, the code worked in both the constructor and the Window_Loaded() method: using System.Windows; namespace TestModuleLoader { public partial class Window1 : Window { public Window1() { InitializeComponent(); }