connection objects with the same name

Results 1 to 2 of 2

Thread: connection objects with the same name

  1. #1
    paul13 Guest

    Default connection objects with the same name

    i am working on a web sight, and every page uses a connection string with the same name. would this cause a slowdown, if more than one person is on a different page, since they are both trying to use the same connection?

  2. #2
    Join Date
    Dec 1969

    Default RE: connection objects with the same name

    I&#039m not 100% sure what you are asking.<BR><BR>Do you mean that you create a connection object and store it as an application value? If so, that&#039s a no-no.<BR><BR>But I suspect you mean something much more mundane than that. I suspect you simply mean that all the users are using the same connection *string*. In which case...<BR><BR>Of course they are! How else could it work? It&#039s designed to work that way, multithreaded and all.<BR><BR>Heck, if you worry about that, why don&#039t you worry about two users each using the same ASP page? No different, really. This is what multiple user operations is all about. Perfectly normal. Keep on truckin&#039!<BR>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts