Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
platform
active.directory
adsi
adsi.iis-admin
base
com_ole
complus_mts
component_svcs
database
directx
gdi
graphics_mm
internet.client
internet.server
internet.server.isapi-dev
localization
mapi
messaging
msi
mslayerforunicode
multimedia
networking
networking.ipv6
sdk_install
security
shell
telephony.tapi_2
telephony.tapi_3
telephony.tsp
telephony.wte
tools
ui
ui_shell
win_base_svcs
win16
  
 
date: Sat, 3 May 2008 19:09:08 -0700,    group: microsoft.public.platformsdk.networking.ipv6        back       


Thoughts on whether to include IPv6 address dialogs   
I have seen suggested on MSDN that IPv6 address dialogs are not needed 
because users would rarely need to manually specify an IPv6 address. 
Especially since IPv6 has improved features such as stateless 
autoconfiguration.  However, I suspect that there will still be times when 
the user will desparately need to enter a manual IPv6 address, such as when 
the DHCP server is not working, or the address is not yet propagated through 
DHCP, or testing and troubleshooting of the network environment, etc.  So 
when building applications should the application include an IPv6 address 
dialog or just skip this?

I can't seem to decide.  After all, as an example, users don't have a dialog 
to change their network card MAC address.  But, on the other hand, in those 
rare times when the user must specify a manual address they will have a hard 
time without a dialog.
date: Sat, 3 May 2008 19:09:08 -0700   author:   fpbear ere

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us