While I dont like "vendor lock in" for myself, I'm a techie. For a serious business customer, vendor lock in is far less of an issue than getting proper support.
On Tue, Aug 10, 2010 at 11:03 AM, L. Aaron Kaplan <[email protected]> wrote: > > On Aug 10, 2010, at 3:26 PM, Ralph wrote: > > Never asked because we don’t use them for making the mesh. We use only > Tropos, although 3 systems we did for another company required Cisco > product. I will never deploy Cisco mess(h) again-LOL. > The Peps are the CPEs we use. In a muni mesh, the CPE radios are clients, > not part of the mesh. > The Pep CPEs work great with Tropos and the Peps were actually the original > recommended CPE for use with Google WiFi in Mountain View when they began. > > > Interesting. > Well, I still believe, RFCs and open standards are the only way to go when > building mesh networks. > Everything else leads to a vendor lock in. > > But nevertheless it is interesting what proprietary vendor mesh solutions > do and how well they perform. > > Is there any way to find out if one mesh solution will interact with a > different vendor's solution? > > a. > > > > > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ >
-------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
