On Thu, 08 Mar 2007 20:36:46 +0100, Johannes Berg wrote: > On Thu, 2007-03-08 at 14:36 -0500, Dan Williams wrote: > > I'd basically expected that this was the model we'd be using anyway. A > > user tool wouldn't have to: > > > > set ssid > > set key > > set authmode > > associate > > > > but instead bundle all those up into one message to netlink with the > > "associate" command or something. > > Right. However, as far as I understood some people at the wireless > summit, they'd prefer having one command that bundles all the settings > and then another one that applies them. Maybe it's just a > misunderstanding on my part and this whole thread is pointless? I think I was one of people who differentiated "config" and "action" calls. The problem with wext is that we don't know when association should take place. (When setting a parameter? Which one?) We need to have a well defined place at which association occurs. I don't care how this is achieved as long as it's fulfilled. One solution is to have a separate (that doesn't mean it cannot be bundled with other commands) "associate" request. There are surely other solutions. Thanks, Jiri -- Jiri Benc SUSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
