Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: Marc Gravell <marc.gravell@xxxxxxxxx>
- Date: Thu, 22 Nov 2007 07:36:25 -0800 (PST)
Using a webservice means that i would need to save my Car object to some
sort of physical location.
Er, why? I simply don't undertand what you mean here... there is no
need to save anything anywhere.
If possible I would like to seamlessly move it
around from Windows form host to web application window, back to windows host
and then into another web form and so on.
They are fundamentally different architectures. The best you can do is
an agreed serialization format, which is exactly what a web-service
does.
I am creating a workflow solution
and this object needs to be available in every hosted web application and
also from the host itself.
There is no *single* object here. Since they are different
architectures on different machines, you can only move a
representation of the Car. And that means it will get cloned. Hence
the need for the web-service (or whatever) to return the updated
representation of the Car when it has completed it's method.
Hmm, i will give webservices a try as well as the serialization of the
object into the .Navigate parameter.
At the most basic level, these two approaches amount to the same
thing. The big difference is that that a web-browser is designed to
show content (mainly HTML) to a human user, and a web-service is
designed to allow two *systems* to talk to each other.
Since the latter is what you are trying to do, this is the pattern
your design should favor. At the very least, if you don't want to use
SOAP web-services, then WebClient or HttpWebRequest are far better
options that a browser if you just want to send a Car (as xml or
whatever) to a Url that does something and returns the updated Car (as
xml or whatever).
Marc
.
- References:
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: Marc Gravell
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: Marc Gravell
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- From: Marc Gravell
- Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Prev by Date: MapVirtualKey doesn't distinguish between left and right keys on XP/2000
- Next by Date: Re: Table bloat in Linq-SQL
- Previous by thread: Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Next by thread: Re: AxShDocVw.AxWebBrowser.Navigate and object headers
- Index(es):
Relevant Pages
|