Re: Help on proper method ????

Hi, Serge:

See my inline comments. Analyzing your business requirements, select a
proper way!

Regards,

Do you know batching, asynchrony and parallel computation with online
compression? See the sample project SocketPro at www.udaparts.com


"calderara" <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:55586CB6-DA81-47CA-AC2F-DD97E6F51B8C@xxxxxxxxxxxxxxxx

OK fine..

Doing this in that way do you think it is better ?
- to read all data from database and store them in memory ready to be push
when request ?.

This is faster, but you may need to write code for synchronizing memory
cache and backend database. Also, you may need to lock the memory cache if
you need to access it from different threads. If your memory cache is too
large, maybe this method is not a proper way.

In short, if you can surely synchronize memory cache and backend
database and memory cache is not too large, this way may be preferred.


- or do you think I should read them from database each time a request is
comming

This way is simpler, but it is slightly slower because a request has to
be sent to a backend database.



thnaks for help
serge
"Spam Catcher" wrote:

=?Utf-8?B?Y2FsZGVyYXJh?= <calderara@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:CCF3D645-CBEA-40D1-BC0F-CDE259F374AC@xxxxxxxxxxxxx:

What do you mean by publisher methode from my applciation side ? is it
just the fact that it send data back to my cllient?

He means to push the events from the server --> client.



.

Relevant Pages

  • Re: Help on proper method ????
    ... you can ping your client from your server. ... I do not need to keep syncronistaion of memeory with back end database ... you may need to lock the memory cache ...
    (microsoft.public.dotnet.framework.remoting)
  • Re: Help on proper method ????
    ... I do not need to keep syncronistaion of memeory with back end database ... becasue data which are pushed are configuration data that never change. ... Whnen a request is coming, I should be abvle to send back message 1, message ... If your memory cache is too ...
    (microsoft.public.dotnet.framework.remoting)