C#

George_George wrote:

1.

It is a local file. Why do you think there may be issues for network based file? For example scenario?

George_George wrote:

2.

The reason why I keep it open is, the content writes to the file depends on ad-hoc client request, if no request, no write operation, if many requests, I need write a lot of stuff. It is impossible to predict the # of request of clients.

 using (System.IO.StreamWriter sr = new System.IO.StreamWriter("filename", true))
 {
    sr.WriteLine("test message");
     sr.Flush();
}

George_George wrote:

My question is, if I obtain the handle of the StreamWriter too long without any write operations (for example, 2 days or longer), will the handle (or the underlying file) be closed by some parties (e.g. CLR, OS, etc.) -- like timeout of socket?

George_George wrote:

whether file will be automatically closed if open too long without any operation?

udikantz wrote:

as im sending same data as my IE agent i dont know what else will work

WebReq.UserAgent = "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 (.NET CLR 3.5.30729)";

protected void Page_Load(object sender, EventArgs e)
   {
       //string strBuffer = "email=" + username + "&pass=" + Password + "&login=Login";
       string strBuffer = "email=xxxxxxxxxxx&pass=xxxxxxxxxxxxx;login=Login";

      start_post(strBuffer);
   }

   public void start_post(string strBuffer)
   {
       //Our postvars
       byte[] buffer = System.Text.Encoding.ASCII.GetBytes(strBuffer);
       //Initialisation

       HttpWebRequest WebReq = (HttpWebRequest)WebRequest.Create("https://login.facebook.com/login.php?m&next=http%3A%2F%2Fm.facebook.com%2Fhome.php");
       //Our method is post, otherwise the buffer (postvars) would be useless
       WebReq.Method = "POST";
       //We use form contentType, for the postvars.

       WebReq.ContentType = "application/x-www-form-urlencoded";
       //The length of the buffer (postvars) is used as contentlength.
       WebReq.ContentLength = buffer.Length;
       //We open a stream for writing the postvars
       WebReq.Referer = "http://www.facebook.com/index.php?";

       Stream PostData = WebReq.GetRequestStream();
       //Now we write, and afterwards, we close. Closing is always important!
       PostData.Write(buffer, 0, buffer.Length);
       PostData.Close();
       //Get the response handle, we have no true response yet!
      // HttpWebResponse WebResp = (HttpWebResponse)WebReq.GetResponse();
      // //Let's show some information about the response
      //WebResp.StatusCode;
      //WebResp.Server;

       //Now, we read the response (the string), and output it.
       using (HttpWebResponse response = (HttpWebResponse)WebReq.GetResponse())
       {
           using (StreamReader reader = new StreamReader(response.GetResponseStream()))
           {
           Response.Write(reader.ReadToEnd());

           }
       }
   }

Member 3919049 wrote:

I assume that each of these compilers has its own JIT functionality. Is this correct?

Member 3919049 wrote:

I have read that the C++ compiler supports function inlining but the C# compiler does not

Member 3919049 wrote:

Has MS updated the C# compiler to support function inlining or does function inlining still not exist in the C# compiler?

Member 3919049 wrote:

Is there any reason why the C# compiler does not do function inlining?

Member 3919049 wrote:

It seems like function inlining would provide a big performance improvement

Member 3919049 wrote:

it seems like MS has already done the work to define this logic for the C++ compiler

Member 3919049 wrote:

so it doesn't seem like it would be too complicated to implement similar logic in the C# compiler....

Christian Graus wrote:

I guess they didn't bother to add it.