More about remoting

[Padu]

I've completed the .net example on remoting and it works fine: a listening
server, a dll with the marshal object and a client.

Now in simple terms, how would I connect to a remote GUI and retrieve the
contents of a text box?

Cheers

Padu

[Roger]

I think you should be retrieving an object from the
Web Server.
Then use that object's fields as you need.
Roger

>
Now in simple terms, how would I connect to a remote GUI and retrieve the
contents of a text box?

Cheers

Padu

[Peter Bromberg [C# MVP]]

Remoting is dead. Unless, perhaps, you are using the IPC channel in .net 2.0
Just my 2 cents. I use named pipes.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Padu" wrote:

I've completed the .net example on remoting and it works fine: a listening
server, a dll with the marshal object and a client.

Now in simple terms, how would I connect to a remote GUI and retrieve the
contents of a text box?

Cheers

Padu

[Padu]

"Peter Bromberg [C# MVP]"

Remoting is dead. Unless, perhaps, you are using the IPC channel in .net
2.0
Just my 2 cents. I use named pipes.
Peter

--

Interesting, you were the first one to say such a thing, everybody else said
remoting is the way to go. Can you elaborate a bit more on why do you think
remoting is dead?

Cheers

Padu

[Peter Bromberg [C# MVP]]

Here are a few links that may "help you to think":

http://weblogs.asp.net/cschittko/arc...27/143388.aspx

http://forums.microsoft.com/msdn/sho...=6214&siteid=1

http://www.dotnetguru2.org/laurentde...&c=1&tb=1&pb=1

http://www.servergeek.com/blogs/mick...6_blog_arc.htm

http://www.theserverside.net/tt/talk...?bandwidth=56k

Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Padu" wrote:

>
"Peter Bromberg [C# MVP]"

Remoting is dead. Unless, perhaps, you are using the IPC channel in .net
2.0
Just my 2 cents. I use named pipes.
Peter

--

Interesting, you were the first one to say such a thing, everybody else said
remoting is the way to go. Can you elaborate a bit more on why do you think
remoting is dead?

Cheers

Padu

[Padu]

"Peter Bromberg [C# MVP]"

Here are a few links that may "help you to think":

http://weblogs.asp.net/cschittko/arc...27/143388.aspx

http://forums.microsoft.com/msdn/sho...=6214&siteid=1

http://www.dotnetguru2.org/laurentde...&c=1&tb=1&pb=1

http://www.servergeek.com/blogs/mick...6_blog_arc.htm

http://www.theserverside.net/tt/talk...?bandwidth=56k

Peter

Thanks for the links. I'll investigate further what Indigo is and what's its
current state.

My app is not related to business objects or scalable distributed objects. I
have to make two apps communicate over LAN (possible internet) as fast as
possible (robotics app) and no big concerns about security or scalability. I
initially thought about plain sockets, but several people (from this
newsgroup) hint that remoting is the best choice.

From the links you gave me, that may still be correct, but I see your point.
Why start development on something that is or will be soon deprecated if
there's something better around. (and what is that?)

Cheers

Padu

[Peter Bromberg [C# MVP]]

I have found that Named Pipes is one of the fastest ways (Sql Server uses
it). If you choose remoting you can use the IPC Channel in .NET 2.0, which
uses named pipes.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Padu" wrote:

"Peter Bromberg [C# MVP]"

Here are a few links that may "help you to think":

http://weblogs.asp.net/cschittko/arc...27/143388.aspx

http://forums.microsoft.com/msdn/sho...=6214&siteid=1

http://www.dotnetguru2.org/laurentde...&c=1&tb=1&pb=1

http://www.servergeek.com/blogs/mick...6_blog_arc.htm

http://www.theserverside.net/tt/talk...?bandwidth=56k

Peter

Thanks for the links. I'll investigate further what Indigo is and what's its
current state.

My app is not related to business objects or scalable distributed objects. I
have to make two apps communicate over LAN (possible internet) as fast as
possible (robotics app) and no big concerns about security or scalability. I
initially thought about plain sockets, but several people (from this
newsgroup) hint that remoting is the best choice.

From the links you gave me, that may still be correct, but I see your point.
Why start development on something that is or will be soon deprecated if
there's something better around. (and what is that?)

Cheers

Padu