Your choices in that case could be using Sockets with
some "custom" protocol. If you still want to use Soap, you
can take a look at the Soap formatter implementation in
the "mono" project:
http://www.go-mono.com
HTH... Alex
--
Alex Yakhnin, eMVP
IntelliProg, Inc.
http://www.intelliprog.com
>-----Original Message-----
>Hello Alex,
>
>thanks for the response.
>
>The events are a dire neccessity. The scenario the
application is running in is
>industrial automation meaning the CF-Client will be used
to control machines.
>This doesn't imply that the CF-Client is running on a
mobile device. Furthermore
>"intelligent" panels are used which have their own
operating system. In many cases
>this is CE.NET.
>The base system uses the "normal" .NET framework and is
running on
>PC's. Theses PCs can be part of the machine itself or
some other "servers".
>Now imagine the following scenario:
>An alarm occurs within the machine (Maybe a temperature
got to high).
>This alarm should be reported to all connected clients.
Now if I would use WebServices
>I have to query in small intervals wether there is an
alarm. In the case of events
>I have to do nothing but subscribe to the event and
handle it in any way.
>
>Of course there would be a problem when the CF-Client is
a mobile client and
>disconnected at the time of the occurence of the alarm.
Nevertheless this is in my
>scenario a special case that requires a special handling
I thought about registering
>the client at the server and using a queue to notify it.
If it is not reachable the queue
>will store the messages to be sent to the client for a
certain amount of time.
>
>Maybe there are some other opinions about my primary
questions.
>
>Cheers,
>
>Lars
>
>"Alex Feinman [MVP]" <(E-Mail Removed)> wrote
in message news:(E-Mail Removed)...
>> What's wrong with using web services? You can expose
your object methods via
>> web service and enjoy the built-in support for xml web
services in CF. The
>> only thing you won't get are events, but that would not
sit well with the
>> mobile device paradigm anyway - these devices are not
always connected
>>
>> "Lars Roith" <(E-Mail Removed)> wrote in
message
>> news:(E-Mail Removed)...
>> > Hello out there,
>> >
>> > I hope someone can give some hints for solving the
following problem:
>> >
>> > I have to access some remoting objects hosted at a
server known to me.
>> > These objects are able to send events. The complete
scenario is working
>> quite well on
>> > platforms using the "real" .Net Framework.
>> >
>> > Now I have the new requirement to support .NET CF
clients.
>> >
>> > As I found out the CF does not support Remoting nor
does it support
>> serialization.
>> >
>> > My questions now are:
>> > * What do I have to do to be able to communicate with
server components
>> the same way
>> > "normal" .NET components do? This also includes
execution/calling
>> methods across the wire.
>> > Is this possible or do I have to implement my own
protocol and generat
>> server and client
>> > proxies that handle the requests and perform the
communication?
>> >
>> > * Is there an easy way to use SOAP as the protocol?
So the CF doesn't have
>> any
>> > serialization support it seems to be a daunting
task to write each
>> message by
>> > hand because the CF doesn't "really" support XML.
(I know it has XML DOM
>> the limitations
>> > seem to be very hard). Nevertheless it would be
much easier for the
>> server side implementation
>> > to have SOAP messages instead of some own binary
format. Or maybe is
>> there a way to rebuild the
>> > BinaryFormatter used in "normal" .NET?
>> >
>> > * If I have to implement my own protocol could you
give me some hints on
>> how to do it?
>> > Maybe there are some BestPractices or relevant
patterns to take care of?
>> >
>> > * Are there BestPractices on how to implement a
proxy? I know there are
>> some patterns.
>> > Maybe someone could give me a link to a sample
implementation.
>> >
>> > Thanks in advance,
>> >
>> > Lars
>> >
>> >
>> >
>> >
>> >
>>
>>
>
>
>.
>
Similar Threads
