Yes, it is possible... You can use ajax for this purpose, but you have to specify timeout not to interrupt the process.... I don't think this is quite good idea because if your Service is really down, you will find it much much later... But if you are not using service, but inner part of your aspx.cs or aspx.vb code, then it should be fine :)
2009/12/9 jack me <[email protected]> > from all answers i understand this is impossible updation without down > time. One solution is we will have to use many servers. while updating we > update on one server(that server will be down for some time till updation > time). > > Means it will be at server level. In coding way it is not possible. ? If we > want at coding level . Is it possible in any way........ > > Regards. > > > > > On Tue, Dec 8, 2009 at 8:58 PM, KeidrickP <[email protected]> wrote: > >> Oh, I definitely agree. >> I hope the OP is reading this.. >> >> >> On Tue, Dec 8, 2009 at 9:27 AM, Jamie Fraser <[email protected]>wrote: >> >>> That was kind of my point! >>> >>> If your site is big enough to require DR facilities, you can use DR to >>> minimise (or negate) downtime. >>> >>> If your site doesn't need DR facilities, what does a small amount of >>> offline time overnight matter? >>> >>> >>> On Tue, Dec 8, 2009 at 3:12 PM, KeidrickP <[email protected]> wrote: >>> >>>> Jamie, >>>> I don't think the OP has a DR database in place, or they probably >>>> wouldn't be posting this question. >>>> >>>> >>>> On Tue, Dec 8, 2009 at 8:59 AM, Jamie Fraser <[email protected]>wrote: >>>> >>>>> Or if you aren't using DB partitioning - upgrade your DR database, >>>>> bring that online, once its up, take your production system offline, >>>>> upgrade >>>>> that and then bring it online again. >>>>> >>>>> None of these are particularly difficult issues for large sites as they >>>>> use multiple servers (hundreds and thousands in the case of Google) and >>>>> for >>>>> a very small site with 1 app & 1 DB server, it isn't a problem having a >>>>> few >>>>> hours downtime overnight. >>>>> >>>>> >>>>> On Tue, Dec 8, 2009 at 2:57 PM, Jamie Fraser >>>>> <[email protected]>wrote: >>>>> >>>>>> On any site which uses load balancing, you'll often use database >>>>>> partitioning too, so stick users to a particular web / db server >>>>>> combination >>>>>> and upgrade groups of servers at a time. >>>>>> >>>>>> >>>>>> On Tue, Dec 8, 2009 at 12:12 PM, Vitaly Maslevskiy < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Sounds good, but, typical situation. DB Schema changed, we have to >>>>>>> update dll's >>>>>>> in which order binaries/DBSchema have to be updated. If we change >>>>>>> schema first, >>>>>>> all apps is not 100% up. Only application updated first and "down" >>>>>>> until first request >>>>>>> has valid state. >>>>>>> >>>>>>> Or? >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2009/12/8 Gunawan Hadikusumo <[email protected]>: >>>>>>> > you need load balancing...... 2 or 3 more IIS server run >>>>>>> simultanously >>>>>>> > >>>>>>> > so you could update those server one by one without distrupting the >>>>>>> current >>>>>>> > connected user. >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > On Tue, Dec 8, 2009 at 6:25 PM, jack me <[email protected]> >>>>>>> wrote: >>>>>>> >> >>>>>>> >> Hi, >>>>>>> >> >>>>>>> >> Is it possible to upload the dll or files without downtime of >>>>>>> website. >>>>>>> >> just for sake of example, if gmail upload some thing new in the >>>>>>> website like >>>>>>> >> chatting facility. After that extended the chat facility with >>>>>>> video. >>>>>>> >> According to me this is without the downtime of the gmail. in same >>>>>>> manner, >>>>>>> >> If i want to make any updation in my website without making down >>>>>>> the site >>>>>>> >> how we can achieve this in .net. >>>>>>> >> >>>>>>> >> Thanks, >>>>>>> >> Jack >>>>>>> > >>>>>>> > >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>> >>>> -- >>>> Keidrick Pettaway >>>> >>>> http://kpettaway.com >>>> >>> >>> >> >> >> -- >> Keidrick Pettaway >> >> http://kpettaway.com >> > >
