Still Need desperate help to start with ASP NET - simplified problems - HELP!!

P

pamelafluente

I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
 
P

pamelafluente

No I am not reinventing it. This is a simplified example. The point
here is I want
to talk with a win application. Not to IIS. In this example it seems
not necessary
but I need to talk to a Win app that does huge processing before and
after
receiving dome data from asp page. I have removed the processing
problem just
to get to the essence of the problem.

You have seen only the surface of the question and not got the real
point.
See my previous posting, in case. Thanks anyway.

-Pam

John Timney (MVP) ha scritto:
 
J

Jacob

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))
 
P

pamelafluente

I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:
 
J

Jacob

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:
You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))
Click to expand...
Click to expand...
 
P

pamelafluente

Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:
You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:
You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
J

Jacob

Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:
You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
P

pamelafluente

That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:
Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:
You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
J

Jacob

There are actually a whole bunch of possibilities in the .NET Framework
for doing what you want, but you seem very set on doing it in a desktop
application on the server, which limits your options (or at least
complicates them).

How extensive is the actual processing that you need to have done? The
question is if it is really worth doing in a separate app.

[email protected] said:
That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:
Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
P

pamelafluente

The processing on the server is very complicate. I have a full featured
application (say thick client)
which does a lot of complicate stuff.

What I wish is to be able to interact with this application through IE
from remote computers.
From what I get, it seems I shoud turn my win application into a Web
Click to expand...
service, in order to talk with IE. I have never done web services. Do
you have suggestion on how can I adapt my application to also act as a
web service capable to interact with IE ?

Also there are some nice visual drag drop features which I would like
to deliver to the IE user, creating a smart client within its browser.
So far I suceeded doing the smart client, see:

http://groups.google.it/group/micro...pnet/browse_frm/thread/14d6d0c70aac4884?hl=it

but I do not know how to make it appear within the browser. I have
seen it done but I do not do how to do it! And also I do not know how
to talk back to the server application. Need a lot of help!!

-Pam

Jacob ha scritto:
There are actually a whole bunch of possibilities in the .NET Framework
for doing what you want, but you seem very set on doing it in a desktop
application on the server, which limits your options (or at least
complicates them).

How extensive is the actual processing that you need to have done? The
question is if it is really worth doing in a separate app.

[email protected] said:
That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:
Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


(e-mail address removed) wrote:
Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
J

Jacob

"The processing on the server is very complicate. I have a full
featured application (say thick client) which does a lot of complicate
stuff."

This is not very informative. But I think the real answer to your
question is to create a handler that inherits from IHttpHandler. The
you can post the textbox information to the handler using AJAX and
display the asynchronous response when it arrives.

I think the reason you never get any replies to your questions about
sending data to be handled by a serverside application is that it is
unorthodox. An AJAX approach is great if the processing is so
complicated that it cannot feasibly be done in the course of a normal
postback.


The processing on the server is very complicate. I have a full featured
application (say thick client)
which does a lot of complicate stuff.

What I wish is to be able to interact with this application through IE
from remote computers.
From what I get, it seems I shoud turn my win application into a Web
Click to expand...
service, in order to talk with IE. I have never done web services. Do
you have suggestion on how can I adapt my application to also act as a
web service capable to interact with IE ?

Also there are some nice visual drag drop features which I would like
to deliver to the IE user, creating a smart client within its browser.
So far I suceeded doing the smart client, see:

http://groups.google.it/group/micro...pnet/browse_frm/thread/14d6d0c70aac4884?hl=it

but I do not know how to make it appear within the browser. I have
seen it done but I do not do how to do it! And also I do not know how
to talk back to the server application. Need a lot of help!!

-Pam

Jacob ha scritto:
There are actually a whole bunch of possibilities in the .NET Framework
for doing what you want, but you seem very set on doing it in a desktop
application on the server, which limits your options (or at least
complicates them).

How extensive is the actual processing that you need to have done? The
question is if it is really worth doing in a separate app.

[email protected] said:
That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:

Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


(e-mail address removed) wrote:
Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
P

pamelafluente

[Yes, complicate means that there are some hundred thousand code lines
(if not million),
which of course one does not want to rewrite in asp. Complex visual
editor (page setter) for magazine pages, etc. Complex data processing
on multiple databases, etc.

The problem is just to web-enable what already exist.]

Is anywhere a code example of that? I have no idea where to start.

Actually I was also thinking (not sure if right) I could add a Web
Service
to the main application and use it to talk with IE.

Also when there is some complicate feature (like a page setter for
newspapers) that
cannot be used by a browser, I could perhaps invoke a local *smart
client*
and use this to make the complicate page setting. When done, it could
talk
via web services to the win appication on the server.

Do you think that this approach could make sense? ???

-pa,

Jacob ha scritto:
"The processing on the server is very complicate. I have a full
featured application (say thick client) which does a lot of complicate
stuff."

This is not very informative. But I think the real answer to your
question is to create a handler that inherits from IHttpHandler. The
you can post the textbox information to the handler using AJAX and
display the asynchronous response when it arrives.

I think the reason you never get any replies to your questions about
sending data to be handled by a serverside application is that it is
unorthodox. An AJAX approach is great if the processing is so
complicated that it cannot feasibly be done in the course of a normal
postback.


The processing on the server is very complicate. I have a full featured
application (say thick client)
which does a lot of complicate stuff.

What I wish is to be able to interact with this application through IE
from remote computers.
From what I get, it seems I shoud turn my win application into a Web
Click to expand...
service, in order to talk with IE. I have never done web services. Do
you have suggestion on how can I adapt my application to also act as a
web service capable to interact with IE ?

Also there are some nice visual drag drop features which I would like
to deliver to the IE user, creating a smart client within its browser.
So far I suceeded doing the smart client, see:

http://groups.google.it/group/micro...pnet/browse_frm/thread/14d6d0c70aac4884?hl=it

but I do not know how to make it appear within the browser. I have
seen it done but I do not do how to do it! And also I do not know how
to talk back to the server application. Need a lot of help!!

-Pam

Jacob ha scritto:
There are actually a whole bunch of possibilities in the .NET Framework
for doing what you want, but you seem very set on doing it in a desktop
application on the server, which limits your options (or at least
complicates them).

How extensive is the actual processing that you need to have done? The
question is if it is really worth doing in a separate app.

(e-mail address removed) wrote:
That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:

Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


(e-mail address removed) wrote:
Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
J

Jacob

You could do it as a web service. However you really wouldn't gain
anything in terms of programming. I think the handler is the way to go.
The handler can draw on the webservice for information and db lookup.
In fact I think we're talking about the same thing. Send a request to
the server to start the processing and then return the result when it's
ready. My advice would be to go with AJAX and asynch response.

IE posts data AJAX to handler on web server
Handler starts processing
Returns response when processing is finished
IE receives response in its asynch response handler and displays it.

[Yes, complicate means that there are some hundred thousand code lines
(if not million),
which of course one does not want to rewrite in asp. Complex visual
editor (page setter) for magazine pages, etc. Complex data processing
on multiple databases, etc.

The problem is just to web-enable what already exist.]

Is anywhere a code example of that? I have no idea where to start.

Actually I was also thinking (not sure if right) I could add a Web
Service
to the main application and use it to talk with IE.

Also when there is some complicate feature (like a page setter for
newspapers) that
cannot be used by a browser, I could perhaps invoke a local *smart
client*
and use this to make the complicate page setting. When done, it could
talk
via web services to the win appication on the server.

Do you think that this approach could make sense? ???

-pa,

Jacob ha scritto:
"The processing on the server is very complicate. I have a full
featured application (say thick client) which does a lot of complicate
stuff."

This is not very informative. But I think the real answer to your
question is to create a handler that inherits from IHttpHandler. The
you can post the textbox information to the handler using AJAX and
display the asynchronous response when it arrives.

I think the reason you never get any replies to your questions about
sending data to be handled by a serverside application is that it is
unorthodox. An AJAX approach is great if the processing is so
complicated that it cannot feasibly be done in the course of a normal
postback.


The processing on the server is very complicate. I have a full featured
application (say thick client)
which does a lot of complicate stuff.

What I wish is to be able to interact with this application through IE
from remote computers.

From what I get, it seems I shoud turn my win application into a Web
service, in order to talk with IE. I have never done web services. Do
you have suggestion on how can I adapt my application to also act as a
web service capable to interact with IE ?

Also there are some nice visual drag drop features which I would like
to deliver to the IE user, creating a smart client within its browser.
So far I suceeded doing the smart client, see:

http://groups.google.it/group/micro...pnet/browse_frm/thread/14d6d0c70aac4884?hl=it

but I do not know how to make it appear within the browser. I have
seen it done but I do not do how to do it! And also I do not know how
to talk back to the server application. Need a lot of help!!

-Pam

Jacob ha scritto:

There are actually a whole bunch of possibilities in the .NET Framework
for doing what you want, but you seem very set on doing it in a desktop
application on the server, which limits your options (or at least
complicates them).

How extensive is the actual processing that you need to have done? The
question is if it is really worth doing in a separate app.

(e-mail address removed) wrote:
That's interesting Jacob. I have actually though about that approach.
But it would be much
neater if I could avoid installations on the client side.

I would like to see * only IE * on the client side and a full
application on the server side.

My problem is I cannot find an easy way to make IE talk with the win
app on the server side
and everytime I ask about it, it seems that none has working examples!
This is quite strange as this problem would seem a really basic one. Or
perhaps I am asking in wrong places...(?)

That IHttpHandler would seem a way to go. But cannot find some
simple explanation on how to integrate that stuff with a win
application.

I have also explored the smart client approach, which probably ios
simila to the applet concept, but then I cannot see an easy way to talk
with the server app.

Another possibily are services, but how do I make it listen to the http
port??

I cannot believe this IE-App talking stuff is so complicate, after all
this is called .NET !

-pam

Jacob ha scritto:

Your program starts in:
Public Shared Sub Main()
End Sub

If you want to pass arguments to the program at startup you can change
that to
Public Shared Sub Main(ByVal Args() As String)
End Sub

Now you can process the entered arguments at startup.

I think what you really want is to make a desktop application that has
an embedded browser. This way you have a two way communication between
browser and program so that you can leave all the client server
communication up to the application and let the browser control handle
the rendering.


(e-mail address removed) wrote:
Thanks Jacob. I didn't get all you are suggesting (I have no idea what
you mean by "have an application that receives the data as arguments in
its startup".) Thanks anyway for the suggestions.

Actually, in other words, what I need is a working example of an ASP
page talking with an object which implements the interface IHttpHandler
within a win application.

For my purposes asp net is totally insufficient. I need to make tal IE
with a win app directly.

Does anybody have some working example or some pointer ?

-Pam

Jacob ha scritto:

You write that there is no IIS involved. This is not true since you are
serving your web page in a browser that requests the page from a
webserver.

Designwise I think it's a bad idea to send the information to be
processed in an external application. When you send the information
back to IIS to send to the client you are going to have to find out
which client sent it (using a session ID I guess). As IIS doesn't
support push technology you have no way of notifying the client that
the information has been successfully processed or it has failed.

But I guess the short and dirty answer to your question is to have an
application that receives the data as arguments in its startup. You the
open the application using System.Diagnostics.Process.Start(). The
process gets the information from the arguments and processes them and
then closes itself down.

Alternatively you pass the information to a database. You processing
app then checks the database every once in a while for new data and
processes it.

Otherwise you need to look into message queueing.


(e-mail address removed) wrote:
I agree that from the example it would seem that ASP is sufficient.

But, as I told you, I have made an oversimplified scenario to make
easier to
answer to the core of the question. You are trying to solve my example,

but my example serves only to show the principle.
I do not just need to send a string back and forth between a IE and
IIS.

I want to tell a win application (server side) what to do from a
browser and viceversa, I want the browser to display what the win
application sends back.

My scheme:

Web client --> Win App (extensive processing) [no IIS involved]
Win App (Extensive processing) --> Web Client

Got it?

Thanks,

-Pam



Jacob ha scritto:

You are definitely overcomplicating this issue. If you want the asp.net
page to return the value to the textbox, you merely use the
Textbox.Text property.

You say you also want to send the Textbox.Text value to an application
running on the server? Why, to feed it into a database? Asp.net can do
that for you. Passing values to other programs is advanced stuff and
you might want to learn the basics first.

Question 3 is obvious -
Response.Write(GenerateResponsePage(Textbox.Text))


(e-mail address removed) wrote:
I am still working with no success on that client/server
problem. I need your help. I will submit simplified versions
of my problem so we can see clearly what is going on.

My model:

A client uses IE to talk with a server.
The user on the client (IE) sees an ASP net page containing
a TextBox. He can write some text in this text box and
push a submit button.

Problem 1. What's the code the ASP NET page?
============================================

A server computer on http://MyServer/MyApp.exe has a .NET
program running. This is a win application which contains
somewhere the following public function:

Function GenerateResponsePage(ByVal ThisIsWhatReceivedFromClient As
String) As String

Dim MyWebPage As String = String.Empty

MyWebPage &= "<html>"
MyWebPage &= vbCrLf & "<Body>"
MyWebPage &= vbCrLf & "Received from client: <br>"
MyWebPage &= vbCrLf & ThisIsWhatReceivedFromClient
MyWebPage &= vbCrLf & "</Body>"
MyWebPage &= vbCrLf & "</html>"

Return MyWebPage

End Function


The win application on the server receives the text submitted in the
text box
(we call it "ThisIsWhatReceivedFromClient") by the user who is using IE
on the client side. As an answer the Server sends back a page generated
by
the function "GenerateResponsePage" and the browser displays it to the
User
on the client side.


Problem 2. How do I make the win application to
receive the text submitted by the user in the TextBox ?
======================================================

Problem 3. How do I make display the string generated by
the "GenerateResponsePage" (simple html page) on the user
browser ?
============================================================

That all for now. My biggest problems are with problems 2 and 3. I need
a simple
working example to get started. Please help!

-Pam
Click to expand...
Click to expand...
Click to expand...
 
J

John Timney \(MVP\)

Then look at the second simple suggestion of creating a webserver in your
windows application.

Web browsers follow the HTTP protocol - they submit requests based on this
protocol over TCP to port 80 (typically) so you have to work within those
constraints if you wish to use a web browser (as you state) as your client.
To respond to a request from a web browser, you need a port listener that
understands the http commands the browser will issue when you post a request
to a remote port.
 
P

pamelafluente

Thank you Jacob and John,

So, to recap, it seems there is a convergence of opinions towards
the IHttpHandler. Unfortunately I cannot find any working
example of implementation around. Is anybody able to provide
an example, perhaps showing how to solve my original simple textbox
problem?

For the part where I have to provide the IE user with a "full client
experience" (like the page setter) do you think that the smart client
way
is the right approach. And, also, can I get the client displayed
within the IE window and communicate with the IHttpHandler ? And how?

It's incredible that there isn't much info around about these basic
tasks. It seems everybody is just doing either plain asp pages or win
apps!

-Pam



 
J

Jacob

I think you will find plenty of examples on the internet that you can
piece together to make your final app. But you will have to work with
both serverside and clientside code.

I think the reason you won't find any cut'n'paste templates on the
internet is that this is fairly advanced stuff and how web programmers
(like myself) make money.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Need help with stripe payment 0
I need help fixing my website 2
Need help with this script 4
Need help with code on website (noob) 2
Desperate 2
Need help , Having problem with Drag n Drop... 1
Help with my responsive home page 2
Help needed with thank you message 5

Members online

No members online now.
Total: 35 (members: 0, guests: 35)
Robots: 493

Forum statistics

Threads
473,769
Messages
2,569,580
Members
45,055
Latest member
SlimSparkKetoACVReview

Latest Threads

Top