On Fri, 24 Jan 2003 16:31:16 +0100, Dejan Jelovic <[EMAIL PROTECTED]>
wrote:
>Dominic Cooney wrote:
>
>> Tail calling is apparently slow because the activation
>> records of the old and new method have to be swapped.
>> Conversely, jmp should be quite fast.
>
>I'm lost. What's an "activation recor
Our web app. uses the IE TreeView WebControl. Each time that control
refreshes itself it leaks handles on the client (using IE6). When you close
IE Windows recovers the handles and memory.
Not a big deal but I was wondering if anyone knows about this?
You can read messages from the Advanced DOTNE
Why don't you just hold onto the Assembly object that comes back from the codedom? I
mean, why discard it, just to go searching for it again, moments later?
-S
On Thu, 23 Jan 2003 17:41:03 -0500, Abdulla, Jehangir <[EMAIL PROTECTED]> wrote:
>I'm using CodeDom to generate an Assembly. I now ne
I brought this up on the MS .NET remoting newsgroup last summer. I can't
believe MS wants us to use TCP for IPC ON THE SAME MACHINE. So inelegant.
You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced
DOTNET, or
subscribe to other DevelopMentor lists at http://discus
Actually we were NOT calling .Close (oops) but we are now and we still see
the memory leak.
I had a similar leak last summer with the IE WebControls TreeView control.
It seemed to be leaking handles whenever the tree was refreshed. We still
haven't found the cause of that. What can leak handles
Sure, sure -- but then how would the listening app publish/communicate that port
number, so that other client apps could connect to it?
I would need some kind of simple, secure, per-session comm. channel for that -- so I'm
back to square one.
In the article you cite, the author seems to use a r
But you get no real benefit , selecting port 0 you are using ip and you
still get in memory IP packest generated to send over the in memory port.
There is nothing here which cant be done its only a question of difficulty
eg easy Remoting - you get the protocol and remoting overheads
l
Dominic Cooney wrote:
> Tail calling is apparently slow because the activation
> records of the old and new method have to be swapped.
> Conversely, jmp should be quite fast.
I'm lost. What's an "activation record"?
Also, does that swapping you are describing need to be done when one is
calling
I could be wrong but if you set 0 as the port that the app should listen
on then the remoting channel picks an "open" port.. now if you load via
TS or fast user switching should this not be a separate process and
different port? Here is the example you "might" be looking for [1]...
HTH
scott
[1]h
I'm using CodeDom to generate an Assembly. I now need to call methods in classes in
that Assembly.
Whats the best way of doing it, I can do a AppDomain.CurrentDomain.GetAssemblies and
loop thru the Assemblies returned until I find my assembly and then use Reflection to
call methods on it, but I
I think the CLI/R is an interesting study in design compromise.
Tail calling is apparently slow because the activation records of the
old and new method have to be swapped. Conversely, jmp should be quite
fast.
Regarding the CLI spec, part of Partition III, Section 2.1 reads:
"There may also be
11 matches
Mail list logo
