Re: Sending Messages and Sharing Objects
- From: Michael Nemtsev <nemtsev@xxxxxxx>
- Date: Sun, 7 May 2006 09:25:28 +0000 (UTC)
Hello Raju,
RJ> Most of the times our software runs in an intranet environment. We
RJ> are using CSLA framework by Rocky because it allows us to switch
RJ> between various channels, viz. Web Service, Remoting or Simple
RJ> 2-Tier architecture. Our product needs to support all these three
RJ> since client requirements could vary.
RJ> For example, one of our clients in Indonesia has offices in three
RJ> different locations. In such case, we use webservices to request for
RJ> information. But mostly its 2-Tier or remoting depending on the
RJ> number of users using the system and the scalability factor.
Can't understand about 2Tiers. Why don't use WS instead of remoting in your case?
RJ> Now, my requirement is, in an Intranet system, using .NET, how can I
RJ> send messages between different physical systems. I want something
RJ> similar to MSN Messenger popups on the task bar.
It's the message-orient system, based on XML messages, as I described in the former post
RJ> And by caching, I mean, caching frequently used data which does not
RJ> gets modified very often, like country, state and city information.
RJ> I mean this data is pretty much constant. May change once or twice a
RJ> year. I mean how often does a new country gets added. right? So, I
RJ> would like to cache this data in some place (local or some other
RJ> central repository) so it can be fetched easily (no need for an
RJ> actual database fetch). But of the odd chance that data might get
RJ> updated, I would like to notify client of the same and refresh the
RJ> cached data list.
I can't see what's wrong with Database solution? The data is consitend and located in one place. You can be sure that there is no variety of the same data. Keep on local? In client? It's possible, but you need additional steps to update this data between clients.
RJ> Any ideas or suggestions. Some one recommended I could create a
RJ> windows service to do this.
Yep, but it's too common.
There is a lot of solutions that u can apply.
Describe your problem more detailed
---100 external users or intenal? Intranet or internet apps?
What do use for the messages XML and XSTL to transfer messages to the
canonical form?
I think remoting will tie you too hard, and it brings a lot of
problems
with indigo.
I recomend to use WS, it's gives u a nice heterogeneity.
What do u mean with "data cache"? Database or what?
Could u specify more details?
The general solution is that.
When patient comes to the consultation either he or operator create
new
record on the webSite with necessary information,
afterthat this record in converted(xslt) in the message (xml) that is
sent
to the server where the message is pushed into the ESB(enterprise
service
bus) and your rule engine decided with component is responsible for
this
message, and you message is parsed by that component. component takes
all
necessary data from DB and generate output message.
RJ> We are currently in the design phase of a distributed system. I
have
RJ> 2 questions with this regard.
RJ> RJ> Our app will be used by 100s of users. I would like to send
messages
RJ> to different terminals at times with information. For example,
lets
RJ> say, in a hospital, when a patient comes for consultation, once
he
RJ> has signed in, I would like to send a message to the
corresponding
RJ> provider that the patient has arrived. Something similar.
RJ> RJ> Secondly, I would like to have a central repository of data
cache
RJ> which can be shared by all. Now, our architecture has been
designed
RJ> to use any of the channels - 2Tier, Web Service or Remoting
RJ> (HTTP/Binary). We are using Rocky's CSLA framework with few
RJ> modifications.
RJ> RJ> Any suggestions or ideas or links to some editorials.
RJ> RJ> Thanks,
RJ> RJ> Raju
RJ> ---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents
do not cease to be insipid." (c) Friedrich Nietzsche
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents do not cease to be insipid." (c) Friedrich Nietzsche
.
- Follow-Ups:
- Re: Sending Messages and Sharing Objects
- From: Raju Joseph
- Re: Sending Messages and Sharing Objects
- References:
- Re: Sending Messages and Sharing Objects
- From: Raju Joseph
- Re: Sending Messages and Sharing Objects
- Prev by Date: Choosing an application design - when to move away from databinding
- Next by Date: RE: Choosing an application design - when to move away from databinding
- Previous by thread: Re: Sending Messages and Sharing Objects
- Next by thread: Re: Sending Messages and Sharing Objects
- Index(es):
Relevant Pages
|