Re: webcatalog approaching max

This WebDNA talk-list message is from

1998


It keeps the original formatting.
numero = 19721
interpreted = N
texte = >There are two possible kinds of scenarios where this problem will arise: >(1) When databases (including carts) need to be synchronized across >servers > >Unfortunately, we face the first scenario. Fortunately, the possible >events during which the servers can go out of sync are very rare (when >items are added to a cart, and when items are purchased). > >I know [TCPSend] context is coming in WebCatalog 3.0, but I'm looking for >someone with practical experience out there: has anybody run a single >ecommerce site on more than one machine successfully? Is anybody familiar >with how the big boys do this? In other words, how are carts ever >synced across servers when somebody uses something like the Cisco >LocalDistributor? > >Another related concern is with redundancy. We'd love to put up a second >machine to be active whenever our first goes down. Anybody doing this? >We have been testing this on twin Mac servers for a few weeks now.We have two copies of the e-commerce site, one on each machine under Web* 3.0. QuickDNS Pro distributes the load between the servers.The sites differ only in two ways: One is labelled www.domain.com the other www2.domain.com in the Web* virtual hosts preference settings. So once a person comes to the site they automatically stay on the same server with the one cart until they are finished, no need to sync the machines.And secondly the 'https' links to the secure servers in the purchase section differ on each site so that they are pointing to the secure Web* server on the same machine that the customer has been assinged.As far as redundancy, (Actually our main reason for doing this) If one server goes down all requests for the site are directed by QDNS to the active server (any customer on line at that instant using the downed machine will lose their cart of course).The only problem I came across was syncing the users.db for our password protected section, it involved writing an admin page that [appends] a record then using [redirect] to the second machines users.db [appends] there too. This still needs a bit of 'fool-proof' fixing before I let the customer loose on it.Paul Associated Messages, from the most recent to the oldest:

    
  1. Re: webcatalog approaching max (PCS Technical Support 1998)
  2. Re: webcatalog approaching max (Paul Willis 1998)
  3. webcatalog approaching max (Mdschoen@aol.com 1998)
>There are two possible kinds of scenarios where this problem will arise: >(1) When databases (including carts) need to be synchronized across >servers > >Unfortunately, we face the first scenario. Fortunately, the possible >events during which the servers can go out of sync are very rare (when >items are added to a cart, and when items are purchased). > >I know [tcpsend] context is coming in WebCatalog 3.0, but I'm looking for >someone with practical experience out there: has anybody run a single >ecommerce site on more than one machine successfully? Is anybody familiar >with how the big boys do this? In other words, how are carts ever >synced across servers when somebody uses something like the Cisco >LocalDistributor? > >Another related concern is with redundancy. We'd love to put up a second >machine to be active whenever our first goes down. Anybody doing this? >We have been testing this on twin Mac servers for a few weeks now.We have two copies of the e-commerce site, one on each machine under Web* 3.0. QuickDNS Pro distributes the load between the servers.The sites differ only in two ways: One is labelled www.domain.com the other www2.domain.com in the Web* virtual hosts preference settings. So once a person comes to the site they automatically stay on the same server with the one cart until they are finished, no need to sync the machines.And secondly the 'https' links to the secure servers in the purchase section differ on each site so that they are pointing to the secure Web* server on the same machine that the customer has been assinged.As far as redundancy, (Actually our main reason for doing this) If one server goes down all requests for the site are directed by QDNS to the active server (any customer on line at that instant using the downed machine will lose their cart of course).The only problem I came across was syncing the users.db for our password protected section, it involved writing an admin page that [appends] a record then using [redirect] to the second machines users.db [appends] there too. This still needs a bit of 'fool-proof' fixing before I let the customer loose on it.Paul Paul Willis

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

repost: sending a down arrow (2000) Error: Too many nested [xxx] contexts (1997) t or f (1997) WCS Newbie question (1997) WebCatalog can't find database (1997) [foundItems] context question --returns some fields but not others-- (2000) RE: type 2 errors with ssl server (1997) webDNA and ASP pages (1997) WCS Newbie question (1997) Problems with totals (1997) Listfiles on network with NT (2000) SKU lookup (1997) View Source from cache (1997) Errata: WCS Newbie question (1997) WCS Newbie question (1997) [include ...] behavior (1997) WebCatalog for guestbook ? (1997) [addlineitems] display (1997) Not really WebCat (1997) WebCatalog Use Question (1997)