SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : WAVX Anyone?
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Kid Rock who wrote (1546)4/6/1998 9:17:00 PM
From: Marc Bejarano  Read Replies (2) of 11417
 
thomas...
you say:
===
Balls~packets of information: lots of them, standard size
Price/bucket~small $value by normal pack size(50 balls)

A. Would it ever be worth building this infrastructure for the range and meter usage this way?
===
yes.... but not for wave's market. the infrastructure you describe would meter the TRANSMISSION of the content, not the content itself. this is what the providers do to charge users of X.25 systems and ATM is often metered like this. i think IPv6 has provisions to ease this type of thing, too. many newer switches (cascades and the like) do this. your phone company is doing this when it charges you /minute a certain rate for calls to mexico.

you then say:
===
Does there even need to be a device that monitors flow at a HARDWARE LEVEL.
===
umm... depends on what we're talking about. you seem to be talking about bit flow, here. for zaksat, it's broadband... broadcast... don't want to meter all those broadcast bits. for your xdsl line, your telco/isp may want to meter the bits because they have to pay their upstream provider for the bandwidth that you are consuming unless they have the data locally cached. but we're not used to that.. we're used to flat monthly fees and /hour charges.

you go on to say:
===
The transfer of information itself does not always equate to the value of the information. Would'nt this need to be more of router technology than a client(PC/NC) thing?
===
you've stated the reason for a wave meter without drawing the conclusion. we can't put this in the router because there are no standards to meter differently based on content at the packet level. routers need to be quick. we can put the meter on a motherboard and pay by the terms that are set up by the content provider based on their business model. there is a need NOW for wave meters in the client. infrastructure isn't in place otherwise to securely meter differently depending on the application.

hope i'm making sense to you,
marc
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  

HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2025 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News