C# Discussion Boards - CodeProject

Luc Pattyn2-Dec-10 5:19

2-Dec-10 5:19

your client code seems OK; I do have a few comments on the server side:

1.
you never have shown the code that launches the first read, i.e. the BeginReceive that sits outside any callback.

2.
I suggested you first receive the length (4 bytes), then one or more large amounts of data; my pseudo-code was using the same buffer for all of these, so it had to set length to 4 initially, and to the actual buffer size later on. I don't see your code do that.

3.
you could always (temporarily) add more logging to better grasp what is going on.

4.
I suggest your first test is with a very small data set, so it fits in one receive buffer. Only when that works you should test larger amounts of data.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at them.

Jacob D Dixon2-Dec-10 6:09

Jacob D Dixon

2-Dec-10 6:09

Ahhhhh ok I see what you are doing now.. but if I'm calling BeginReceive again within the Callback then I don't think that will work. Because the first thing you are doing is checking if Length == 0. There are two times this will happen... for the first BeginReceive and also when we read all the bytes (because we know we are done reading when Length == 0).

I get the idea.. unless I'm missing smoething.. changing it now

Luc Pattyn2-Dec-10 6:30

2-Dec-10 6:30

you kick off the receiving actions outside the callback once, then continue the process by issuing another receive inside the callback until you had enough. And length holds the amount still to be received, so once you got it all, you don't issue a new beginreceive, so the callback isn't called any more, the only time it is called with length zero is at the start of a conversation.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at them.

Jacob D Dixon2-Dec-10 7:56

Jacob D Dixon

2-Dec-10 7:56

Ah yeah I got it now. Luc I just want to thank you for your help. Here is what I have now and it seems to be working well:

int bytesRead = handler.EndReceive(iar);
                if (bytesRead > 0)
                {
                    if (state.Length == 0)
                    {
                        state.Length = BitConverter.ToInt32(state.buffer, 0);

                        Logging.Log(handler.RemoteEndPoint.ToString() + " is about to send " + state.Length.ToString() + " bytes", true);
                        handler.BeginReceive(state.buffer, 0, StateObject.BufferSize, 0,
                            new AsyncCallback(ReadCallback), state);
                    }
                    else
                    {
                        state.Length -= bytesRead;
                        state.ms.Write(state.buffer, 0, bytesRead);

                        if (state.Length > 0)
                            handler.BeginReceive(state.buffer, 0, StateObject.BufferSize, 0,
                                new AsyncCallback(ReadCallback), state);
                        else
                        {
                            Logging.Log("Finished receiving " + state.ms.Length.ToString() + " bytes from " +
                                            handler.RemoteEndPoint.ToString(), true);

                            state.ms.Seek(0, SeekOrigin.Begin);
                            IFormatter formatter = new BinaryFormatter();
                            object receivedObject = null;

                            try
                            {
                                receivedObject = formatter.Deserialize(state.ms);

Luc Pattyn2-Dec-10 8:20

Trying to deal with the memory leak in the Flash Player

2-Dec-10 8:20

Hi Jacob,

you're welcome. Glad you got it working reliably.

BTW: You could still reduce your code by sharing the read-more stuff, look again at my pseudo-code[^].

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, improve readability, and make me actually look at them.

jbradshaw1-Dec-10 6:09

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 6:09

I had posted a question a while ago that asked how I could destroy an object in a windows program (the Flash player) and recreate it because there's a memory leak in the player. It's not huge but if you leave it around long enough it eventually will kill the system.

I got a response that said to put the player in a different application domain. Could somebody explain that please? I've read up on application domains and don't see how I would be able to use it.

What about putting a window in a different process and then have it display the flash. When it's done, it could close the window and kill itself. (at least I think I could do that.) Would that solve the memory leak?

TIA - Jeff.

Luc Pattyn1-Dec-10 6:52

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 6:52

why didn't you ask in the thread where you got the advice, so that person (my bet is on Pete) could get a notification e-mail and reply right away?

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

jbradshaw1-Dec-10 7:27

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 7:27

I went searching for it and couldn't find it. I am not sure if I asked it here or in the Microsoft forums.

J.

jbradshaw1-Dec-10 7:32

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 7:32

Whoops! I found the message. It's http://www.codeproject.com/Messages/3630835/Memory-Leak-using-Flash.aspx[^]

So if you are going to respond to this, please do it there.....

Sorry for the confusion.

Jeff.

Luc Pattyn1-Dec-10 7:42

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 7:42

jbradshaw wrote:
So if you are going to respond ...

I won't, however I will try and learn from any replies you'll get.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Pete O'Hanlon1-Dec-10 9:39

1-Dec-10 9:39

Luc Pattyn wrote:
so that person (my bet is on Pete)

How did you guess?

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Re: Trying to deal with the memory leak in the Flash Player

Luc Pattyn1-Dec-10 10:09

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 10:09

I have a memory problem, and it isn't the more common one. I did remember the original thread well, and was hoping for a rather detailed reply. I think an article is in order...

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

Pete O'Hanlon1-Dec-10 10:23

1-Dec-10 10:23

Luc Pattyn wrote:
I did remember the original thread well, and was hoping for a rather detailed reply. I think an article is in order...

OK - I get the hint. I'll see what I can do for you.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Re: Trying to deal with the memory leak in the Flash Player

Luc Pattyn1-Dec-10 11:07

Re: Trying to deal with the memory leak in the Flash Player

1-Dec-10 11:07

Thanks. I'm looking forward already.

Smile | :)

Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] Nil Volentibus Arduum

Please use <PRE> tags for code snippets, they preserve indentation, and improve readability.

DaveyM692-Dec-10 9:44

DaveyM69

2-Dec-10 9:44

I'll be looking out for it too! Thumbs Up | :thumbsup:

Dave

Binging is like googling, it just feels dirtier.
Please take your VB.NET out of our nice case sensitive forum.
Astonish us. Be exceptional. (Pete O'Hanlon)

BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn)

Re: Trying to deal with the memory leak in the Flash Player

Pete O'Hanlon1-Dec-10 9:12

1-Dec-10 9:12

jbradshaw wrote:
What about putting a window in a different process and then have it display the flash. When it's done, it could close the window and kill itself. (at least I think I could do that.) Would that solve the memory leak?

Exactly. That was what I was talking about. Basically you'd have a sentinel application that existed purely to create these app domains which host the application.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Re: Trying to deal with the memory leak in the Flash Player

Pete O'Hanlon1-Dec-10 22:47

1-Dec-10 22:47

Jeff - Luc's persuaded me to write an article on this (it wouldn't be the first time), so I'll pull one together and post it here on CP. Hopefully this will demonstrate what I've been suggesting.

I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be

Forgive your enemies - it messes with their heads

Re: Trying to deal with the memory leak in the Flash Player

jbradshaw2-Dec-10 2:42

2-Dec-10 2:42

Wow! I feel so special!

Thanks for all of your help.

Jeff.

Web Application Timeout

MWRivera1-Dec-10 5:48

1-Dec-10 5:48

Hi All,

We have a web application that timesout when the user is in a textbox typing. If the user moves out of the text box however, the timeout period appears to be reset. Is there a way to prevent the web application timing out (reset the timeout period) when the is typing in a textbox?
Our users access the web application using IE.

Thank you,
Mel

T M Gray1-Dec-10 5:51

T M Gray

1-Dec-10 5:51

What kind of timeout? Is it a session timeout? What is your code doing when the user moves out of the textbox?

MWRivera1-Dec-10 6:26

1-Dec-10 6:26

Yes, this is a session timeout.
There is no code that states if the user moves from one field to another, restart the timeout session time.
If I understand correctly this is the default behaviour of a session. Please correct me if I'm wrong. Any advice/help would really be appreciated.

Thank you,
Mel

MWRivera1-Dec-10 6:28

1-Dec-10 6:28

Maybe someone knows of a way to renew the session on keystroke within a textbox?

Thanks

Dave Kreskowiak1-Dec-10 7:16

Dave Kreskowiak

1-Dec-10 7:16

That would take a roundtrip to the server and a refresh of the page. The default session timeout for IIS is, I believe, 20 minutes.

I think a better solution would be to create a very small frame in your page that refreshes itself every 15 minutes or just short of whatever your session timeout is.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

MWRivera2-Dec-10 3:47

2-Dec-10 3:47

Dave, thank you for your reply.

Are you suggesting I put a frame in the page and then within the frame put the textbox? Would I then be able to refresh the page through the frame when a character is entered in the textbox, therefore refreshing the session on keystroke?
The reason for this is that I want the session to expire if the user has no interaction for a period of time, but if there is activity including text entered in the textbox then I want the session renewed.

Thank you,
Mel