By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,101 Members | 1,394 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,101 IT Pros & Developers. It's quick & easy.

Data availablility best practices?

P: n/a
I have a client that wants me to code a simple application as a prototype.
The catch is that he wants to use this application at several different
stores while being able to share each store's data. He also want the
application to continue to function in the case that the internet is down
for any reason.

I have my own theories as to how to accomplish this shared data environment,
but I'd love to hear your ideas about sharing data real-time (when the
connection is available) and being able to continue to run even when the
connectivity to other stores or a main data storage server is unavailable.

Keeping bandwidth and complexity to a minimum are desired characteristics.

Thanks!
Mar 23 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Jim,

Will you be so kind as you use a newsreader as Outlook Express not to
multipost.

Crossposting with that is easy by sending the message to more newsgroups at
once. We can than deal in the experiences and the answers.

I have answered this question in another newsgroup.

Thanks in advance.

Cor

"Jim Hubbard" <re***@groups.please> schreef in bericht
news:Av*****************@bignews3.bellsouth.net...
I have a client that wants me to code a simple application as a prototype.
The catch is that he wants to use this application at several different
stores while being able to share each store's data. He also want the
application to continue to function in the case that the internet is down
for any reason.

I have my own theories as to how to accomplish this shared data
environment, but I'd love to hear your ideas about sharing data real-time
(when the connection is available) and being able to continue to run even
when the connectivity to other stores or a main data storage server is
unavailable.

Keeping bandwidth and complexity to a minimum are desired characteristics.

Thanks!

Mar 23 '06 #2

P: n/a
Cor,

Certainly, I will never multipost again. In fact, I will make no
mistake of any kind (on the web or off) from this moment forward - just for
you.

I know that you do not make mistakes as grievous as the one that I so
blatantly conceived and executed here. And, I offer my sincerest apologies
for wasting your most precious and valuable time.

Who knows, with the time that I wasted of yours both reading my mistake
and forcing you to police the newsgroups for crimes like mine, you may have
ended world hunger, stopped global terrorism or even helped Microsoft get
Vista shipped on time.

For stopping you dead in your tracks on these most noble pursuits, I
offer my heartfelt and sincerest apologies. I know that nothing that I can
ever do will repair the damage that I have done to your efforts to combat
these atrocities.

All I can hope for is that YOU forgive my most grievous error.

Perhaps I can one day ascend to the heights of those perfected MVPs
(such as yourself) who have never made such an unforgivable mistake.

In return, I forgive you for the non-answer that you did post in
response to my cries for help.

Jim Hubbard


"Cor Ligthert [MVP]" <no************@planet.nl> wrote in message
news:ea**************@TK2MSFTNGP09.phx.gbl...
Jim,

Will you be so kind as you use a newsreader as Outlook Express not to
multipost.

Crossposting with that is easy by sending the message to more newsgroups
at once. We can than deal in the experiences and the answers.

I have answered this question in another newsgroup.

Thanks in advance.

Cor

"Jim Hubbard" <re***@groups.please> schreef in bericht
news:Av*****************@bignews3.bellsouth.net...
I have a client that wants me to code a simple application as a prototype.
The catch is that he wants to use this application at several different
stores while being able to share each store's data. He also want the
application to continue to function in the case that the internet is down
for any reason.

I have my own theories as to how to accomplish this shared data
environment, but I'd love to hear your ideas about sharing data real-time
(when the connection is available) and being able to continue to run even
when the connectivity to other stores or a main data storage server is
unavailable.

Keeping bandwidth and complexity to a minimum are desired
characteristics.

Thanks!


Mar 24 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.