Passive mode

Please can someone explain the significance of selecting passive mode when
connecting with FTP in VS 2005 or 2008
Is selecting it likely to prevent VS2008 repeatedly downloading he same
files when I change page?
Jaezftp use two tcp/ip connections, one for traffic each way. in active (the
original ftp mode) the client opens one, and the server opens the other.
this required the client to have a port open thru the firewall, so
passive mode was added. in this mode the client opens both connection to
the server. after the connections are established, there is no difference.
-- bruce (sqlwork.com)
jaems wrote:
> Please can someone explain the significance of selecting passive mode
> when connecting with FTP in VS 2005 or 2008
> Is selecting it likely to prevent VS2008 repeatedly downloading he same
> files when I change page?
> Jaez
Technically, the two ports are for "command" and "data" and are not
directional. But yes, passive mode allows the client to initiate both
connections which alleviates many firewall issues. Selection of "passive"
mode has no effect beyond establishing the "data" connection (assuming, of
course, that both client & server support passive mode).
http://slacksite.com/other/ftp.html
"bruce barker" <nospam@.nospam.com> wrote in message
news:u0WPsplcIHA.4436@.TK2MSFTNGP05.phx.gbl...
> ftp use two tcp/ip connections, one for traffic each way. in active (the
> original ftp mode) the client opens one, and the server opens the other.
> this required the client to have a port open thru the firewall, so passive
> mode was added. in this mode the client opens both connection to the
> server. after the connections are established, there is no difference.
> -- bruce (sqlwork.com)
> jaems wrote:

Password Field

Have a textbox that's in Password mode on a user creation page. Have
several dropdowns that cause a PostBack out of necessity on this page. I
cannot separate them. When one of these dropdowns changes, the textbox's
value is lost. How do I prevent this?

Thanksthe best way would be to remember it from the original postback, so it only
passes over the network once. otherwise you can use a hack, and set the
control's "value" attribute.

-- bruce (sqlwork.com)

"James" <minorkeys@.gmail.com> wrote in message
news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
> Have a textbox that's in Password mode on a user creation page. Have
> several dropdowns that cause a PostBack out of necessity on this page. I
> cannot separate them. When one of these dropdowns changes, the textbox's
> value is lost. How do I prevent this?
> Thanks
Can I? I've tried setting it in my Page Load event and it doesn't seem to
persist. I've also tried using a client side control with runat=server.
None of the above seem to want to let me set the value.

"Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
> the best way would be to remember it from the original postback, so it
> only passes over the network once. otherwise you can use a hack, and set
> the control's "value" attribute.
> -- bruce (sqlwork.com)
>
> "James" <minorkeys@.gmail.com> wrote in message
> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>> Have a textbox that's in Password mode on a user creation page. Have
>> several dropdowns that cause a PostBack out of necessity on this page. I
>> cannot separate them. When one of these dropdowns changes, the textbox's
>> value is lost. How do I prevent this?
>>
>> Thanks
>>
You have to do it on the client side using javascript.

Losing the value of a password field is pretty standard. If the password
field is the last one on your page, it should in theory be the last field a
user fills in, so it geting emptied shouldn't really happen.

"James" <minorkeys@.gmail.com> wrote in message
news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
> Can I? I've tried setting it in my Page Load event and it doesn't seem to
> persist. I've also tried using a client side control with runat=server.
> None of the above seem to want to let me set the value.
> "Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
> news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
>> the best way would be to remember it from the original postback, so it
>> only passes over the network once. otherwise you can use a hack, and set
>> the control's "value" attribute.
>>
>> -- bruce (sqlwork.com)
>>
>>
>>
>> "James" <minorkeys@.gmail.com> wrote in message
>> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>>> Have a textbox that's in Password mode on a user creation page. Have
>>> several dropdowns that cause a PostBack out of necessity on this page.
>>> I cannot separate them. When one of these dropdowns changes, the
>>> textbox's value is lost. How do I prevent this?
>>>
>>> Thanks
>>>
>>
>>
JavaScript doesn't seem to work either. It isn't the last field they will
enter, and even if it were, there's no way they'd go for that =/.

"Marina" <someone@.nospam.com> wrote in message
news:OTk4sojEGHA.524@.TK2MSFTNGP09.phx.gbl...
> You have to do it on the client side using javascript.
> Losing the value of a password field is pretty standard. If the password
> field is the last one on your page, it should in theory be the last field
> a user fills in, so it geting emptied shouldn't really happen.
> "James" <minorkeys@.gmail.com> wrote in message
> news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
>> Can I? I've tried setting it in my Page Load event and it doesn't seem
>> to persist. I've also tried using a client side control with
>> runat=server. None of the above seem to want to let me set the value.
>>
>> "Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
>> news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
>>> the best way would be to remember it from the original postback, so it
>>> only passes over the network once. otherwise you can use a hack, and set
>>> the control's "value" attribute.
>>>
>>> -- bruce (sqlwork.com)
>>>
>>>
>>>
>>> "James" <minorkeys@.gmail.com> wrote in message
>>> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>>>> Have a textbox that's in Password mode on a user creation page. Have
>>>> several dropdowns that cause a PostBack out of necessity on this page.
>>>> I cannot separate them. When one of these dropdowns changes, the
>>>> textbox's value is lost. How do I prevent this?
>>>>
>>>> Thanks
>>>>
>>>
>>>
>>
>>
I know for a fact that if you set the value on an input control that is a
password type in javascript, that it does get set correctly. Maybe you need
to post your code then.

I bet your users will like the fact that their password is being sent in
clear text in the browser even less then having to retype their password,
since that is the only way to preserve it in between posts. I would
recommend either accepting that passwords will be blank between posts (this
happens pretty much in every other registration system), re-organize your
registration in such a way that the password gets its own page and it is the
last page in the registration process, or code using the javascript solution
and have the password be sent in clear text - which should be the last
resort.

"James" <minorkeys@.gmail.com> wrote in message
news:uzLRXrjEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> JavaScript doesn't seem to work either. It isn't the last field they will
> enter, and even if it were, there's no way they'd go for that =/.
> "Marina" <someone@.nospam.com> wrote in message
> news:OTk4sojEGHA.524@.TK2MSFTNGP09.phx.gbl...
>> You have to do it on the client side using javascript.
>>
>> Losing the value of a password field is pretty standard. If the password
>> field is the last one on your page, it should in theory be the last field
>> a user fills in, so it geting emptied shouldn't really happen.
>>
>> "James" <minorkeys@.gmail.com> wrote in message
>> news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
>>> Can I? I've tried setting it in my Page Load event and it doesn't seem
>>> to persist. I've also tried using a client side control with
>>> runat=server. None of the above seem to want to let me set the value.
>>>
>>> "Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
>>> news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
>>>> the best way would be to remember it from the original postback, so it
>>>> only passes over the network once. otherwise you can use a hack, and
>>>> set the control's "value" attribute.
>>>>
>>>> -- bruce (sqlwork.com)
>>>>
>>>>
>>>>
>>>> "James" <minorkeys@.gmail.com> wrote in message
>>>> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>>>>> Have a textbox that's in Password mode on a user creation page. Have
>>>>> several dropdowns that cause a PostBack out of necessity on this page.
>>>>> I cannot separate them. When one of these dropdowns changes, the
>>>>> textbox's value is lost. How do I prevent this?
>>>>>
>>>>> Thanks
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
Thanks for the help, this seems to work on Postback:

tbPassword.Attributes("value") = tbPassword.Text

"Marina" <someone@.nospam.com> wrote in message
news:eKbInxjEGHA.216@.TK2MSFTNGP15.phx.gbl...
>I know for a fact that if you set the value on an input control that is a
>password type in javascript, that it does get set correctly. Maybe you
>need to post your code then.
> I bet your users will like the fact that their password is being sent in
> clear text in the browser even less then having to retype their password,
> since that is the only way to preserve it in between posts. I would
> recommend either accepting that passwords will be blank between posts
> (this happens pretty much in every other registration system), re-organize
> your registration in such a way that the password gets its own page and it
> is the last page in the registration process, or code using the javascript
> solution and have the password be sent in clear text - which should be the
> last resort.
> "James" <minorkeys@.gmail.com> wrote in message
> news:uzLRXrjEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>> JavaScript doesn't seem to work either. It isn't the last field they
>> will enter, and even if it were, there's no way they'd go for that =/.
>>
>> "Marina" <someone@.nospam.com> wrote in message
>> news:OTk4sojEGHA.524@.TK2MSFTNGP09.phx.gbl...
>>> You have to do it on the client side using javascript.
>>>
>>> Losing the value of a password field is pretty standard. If the
>>> password field is the last one on your page, it should in theory be the
>>> last field a user fills in, so it geting emptied shouldn't really
>>> happen.
>>>
>>> "James" <minorkeys@.gmail.com> wrote in message
>>> news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
>>>> Can I? I've tried setting it in my Page Load event and it doesn't seem
>>>> to persist. I've also tried using a client side control with
>>>> runat=server. None of the above seem to want to let me set the value.
>>>>
>>>> "Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
>>>> news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
>>>>> the best way would be to remember it from the original postback, so it
>>>>> only passes over the network once. otherwise you can use a hack, and
>>>>> set the control's "value" attribute.
>>>>>
>>>>> -- bruce (sqlwork.com)
>>>>>
>>>>>
>>>>>
>>>>> "James" <minorkeys@.gmail.com> wrote in message
>>>>> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>>>>>> Have a textbox that's in Password mode on a user creation page. Have
>>>>>> several dropdowns that cause a PostBack out of necessity on this
>>>>>> page. I cannot separate them. When one of these dropdowns changes,
>>>>>> the textbox's value is lost. How do I prevent this?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>

Password Field

Have a textbox that's in Password mode on a user creation page. Have
several dropdowns that cause a PostBack out of necessity on this page. I
cannot separate them. When one of these dropdowns changes, the textbox's
value is lost. How do I prevent this?
Thanksthe best way would be to remember it from the original postback, so it only
passes over the network once. otherwise you can use a hack, and set the
control's "value" attribute.
-- bruce (sqlwork.com)
"James" <minorkeys@.gmail.com> wrote in message
news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
> Have a textbox that's in Password mode on a user creation page. Have
> several dropdowns that cause a PostBack out of necessity on this page. I
> cannot separate them. When one of these dropdowns changes, the textbox's
> value is lost. How do I prevent this?
> Thanks
>
Can I? I've tried setting it in my Page Load event and it doesn't seem to
persist. I've also tried using a client side control with runat=server.
None of the above seem to want to let me set the value.
"Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
> the best way would be to remember it from the original postback, so it
> only passes over the network once. otherwise you can use a hack, and set
> the control's "value" attribute.
> -- bruce (sqlwork.com)
>
> "James" <minorkeys@.gmail.com> wrote in message
> news:ODtJUcjEGHA.516@.TK2MSFTNGP15.phx.gbl...
>
You have to do it on the client side using javascript.
Losing the value of a password field is pretty standard. If the password
field is the last one on your page, it should in theory be the last field a
user fills in, so it geting emptied shouldn't really happen.
"James" <minorkeys@.gmail.com> wrote in message
news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
> Can I? I've tried setting it in my Page Load event and it doesn't seem to
> persist. I've also tried using a client side control with runat=server.
> None of the above seem to want to let me set the value.
> "Bruce Barker" <brubar_nospamplease_@.safeco.com> wrote in message
> news:umI$3ijEGHA.2012@.TK2MSFTNGP14.phx.gbl...
>
JavaScript doesn't seem to work either. It isn't the last field they will
enter, and even if it were, there's no way they'd go for that =/.
"Marina" <someone@.nospam.com> wrote in message
news:OTk4sojEGHA.524@.TK2MSFTNGP09.phx.gbl...
> You have to do it on the client side using javascript.
> Losing the value of a password field is pretty standard. If the password
> field is the last one on your page, it should in theory be the last field
> a user fills in, so it geting emptied shouldn't really happen.
> "James" <minorkeys@.gmail.com> wrote in message
> news:%235n36mjEGHA.3200@.tk2msftngp13.phx.gbl...
>
I know for a fact that if you set the value on an input control that is a
password type in javascript, that it does get set correctly. Maybe you need
to post your code then.
I bet your users will like the fact that their password is being sent in
clear text in the browser even less then having to retype their password,
since that is the only way to preserve it in between posts. I would
recommend either accepting that passwords will be blank between posts (this
happens pretty much in every other registration system), re-organize your
registration in such a way that the password gets its own page and it is the
last page in the registration process, or code using the javascript solution
and have the password be sent in clear text - which should be the last
resort.
"James" <minorkeys@.gmail.com> wrote in message
news:uzLRXrjEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> JavaScript doesn't seem to work either. It isn't the last field they will
> enter, and even if it were, there's no way they'd go for that =/.
> "Marina" <someone@.nospam.com> wrote in message
> news:OTk4sojEGHA.524@.TK2MSFTNGP09.phx.gbl...
>
Thanks for the help, this seems to work on Postback:
tbPassword.Attributes("value") = tbPassword.Text
"Marina" <someone@.nospam.com> wrote in message
news:eKbInxjEGHA.216@.TK2MSFTNGP15.phx.gbl...
>I know for a fact that if you set the value on an input control that is a
>password type in javascript, that it does get set correctly. Maybe you
>need to post your code then.
> I bet your users will like the fact that their password is being sent in
> clear text in the browser even less then having to retype their password,
> since that is the only way to preserve it in between posts. I would
> recommend either accepting that passwords will be blank between posts
> (this happens pretty much in every other registration system), re-organize
> your registration in such a way that the password gets its own page and it
> is the last page in the registration process, or code using the javascript
> solution and have the password be sent in clear text - which should be the
> last resort.
> "James" <minorkeys@.gmail.com> wrote in message
> news:uzLRXrjEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>