Re: question on synchronization for Intel Developer Services artic
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 01/27/05
- Next message: Andrew J. Kelly: "Re: controlling temdb size"
- Previous message: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- In reply to: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Next in thread: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Reply: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 21:32:10 -0500
Sure, just keep in mind this is my personal opinion based on my real life
experiences and am not trying to dictate how future apps will be built<g>.
-- Andrew J. Kelly SQL MVP "Geoff" <Geoff@discussions.microsoft.com> wrote in message news:D8AD9D1A-BCEA-48E3-8262-0FC6008EEECB@microsoft.com... > Thanks, Andrew. May I quote you on this in my article? > Geoff gkoch AT stanfordalumn DOT org > > "Andrew J. Kelly" wrote: > >> Well I can't say I have given this a lot of thought lately but yes there >> are >> definite advantages and productivity gains to be had by using >> applications >> that can work the way you need when disconnected. As such a certain >> percentage of new software will be written to take advantage of that. >> That >> does not mean everything will change but many professions are already >> demanding remote or offline access today. >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "Geoff" <Geoff@discussions.microsoft.com> wrote in message >> news:5F224D8D-4278-450F-B04F-11BFC5DC1687@microsoft.com... >> > Thanks, Andrew. Can I bounce another, higher level question off you? >> > >> > The gist of my article is that the tipping point for asynchronous, OC >> > applications is mobile repair and service personnel. Here's a case >> > study >> > that >> > the Intel guys like: >> > http://www.ianywhere.com/success_stories/burlington_north.html. >> > >> > The idea generally is that IT infrastructure is already in place in >> > standard >> > office & enterprise environments. So there's inertia when there's any >> > talk >> > of >> > changing the infrastructure from always-on to sometimes-on, even when >> > there's >> > problems. (For instance, if you're working connected via Wi-Fi to >> > Outlook, >> > SAP perhaps a CRM program, and then you walk from floor to floor, >> > changing >> > subnets and walking in and out WiFi hotspots, you'll often get lots of >> > error >> > messages.) But when the office/white collar-types see the productivity >> > gains >> > service/maintenance personnel get from working in OC fashion, then the >> > white >> > collar workers demand the same kind infrastructure, etc., etc. >> > >> > I guess my questions is, do you buy it? That giving service/maintenance >> > workers mobile applications that work well with sporadic network >> > connectivity >> > (perhaps wireless, perhaps ethernet, perhaps dial-up) will be the >> > tipping >> > point to change the way lots of sw is architected? >> > >> > Thanks, >> > Geoff >> > >> > >> > "Andrew J. Kelly" wrote: >> > >> >> If you are talking about replication then any of the SQL Server >> >> editions >> >> can >> >> do some form of replication, not just CE. What edition will run on >> >> your >> >> mobile device depends on what OS it is running. ADO.net has a lot of >> >> features based around offline datasets and make it relatively easy to >> >> build >> >> applications that can work off line and update later. I would suggest >> >> you >> >> have a look at www.microsoft.com/sql and browse around in the >> >> different >> >> areas that may be of interest to you. >> >> >> >> -- >> >> Andrew J. Kelly SQL MVP >> >> >> >> >> >> "Geoff" <Geoff@discussions.microsoft.com> wrote in message >> >> news:9E776F8F-AA13-432F-B40C-78C3A2AA5DD1@microsoft.com... >> >> > I'm a freelance tech writer working on an article for Intel >> >> > Developer >> >> > Services, Intel's site for sw developers. The article is on writing >> >> > applications for use in occasionally connected environments. Intel >> >> > really >> >> > thinks that asynchronous, OC apps make more sense for a slew of >> >> > mobile >> >> > applications. >> >> > >> >> > Here is my question (I'm sorry if it's naive.... I'm not a >> >> > developer): >> >> > As >> >> > I >> >> > understand it, it's only in SQL for Windows CE that the database can >> >> > live >> >> > locally on the client device, synchronizing to a back end when a >> >> > connection >> >> > becomes available. So building OC solutions across multiple devices >> >> > is >> >> > difficult, because there's little support for the same functionality >> >> > on >> >> > PCs >> >> > laptops. Is this correct? What are are some tips for developers >> >> > looking >> >> > to >> >> > build apps that work asynchronously on laptops? >> >> > >> >> > Thanks very much for any help you can provide. I'm looking for >> >> > comments >> >> > I >> >> > might quote from in my article, but if you prefer not to be quoted, >> >> > that's >> >> > fine, too. I'm also looking just to get smart on this. >> >> > >> >> > -- >> >> > Geoff Koch (gkoch AT stanfordalumni DOT org) >> >> > Science/Tech Writer >> >> > Lansing, Michigan >> >> >> >> >> >> >> >> >>
- Next message: Andrew J. Kelly: "Re: controlling temdb size"
- Previous message: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- In reply to: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Next in thread: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Reply: Geoff: "Re: question on synchronization for Intel Developer Services artic"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
