Of course if you really dig into things you realize the only change you have made is from:
a developer creating a plugin that interacts with a web service
a developer creating a plugin that interacts with an osdash service that interacts with a web service
Minor savings in time, additional layer of abstraction, additional potential point of failure. When you deal with server localization you also have a loss in speed and increase in latency. For front ends which have cross-platform plugins, there really aren't any advantages to 90% of the services offered. Then we add in that quite a few providers (facebook and twitter come to mind) don't allow mitm (man in the middle) services to handle user credentials or cache any data which completely rules them out as osdash services.
Not saying there isn't that 10%...mainly remote access or online data storage...just that almost all of the original ideas for osdash services fall into the above.
Interesting, thanks for the explanation. I just don't like this "move back to mainframes", PC "computers getting dumber like terminals", that the whole idea looks like. But if it works, hey, you can't argue with that. Good luck.
Right. The important point that isn't captured there is that the services in OSDash are stored on the web.
Originally Posted by justchat_1
The OSDash model shouldn't be considered a monolithic replacement for plugins. It isn't. It's more of a plug-in of sorts itself. And, it's good for some things, but not other things.
For example, you can make a plug-in for your car pc that will read from the open source file of car PIDs for OBDII. However, as new cars are added, you'll need to update the file for your FE. OSDash could read the updated file from the web as a service, requiring only the web file to be updated a single time. Additional features of the service might suggest ways to troubleshoot the issue by finding posts in forums related to the trouble code.
On the other hand, it wouldn't make sense for OSDash to send real time data from your engine to a web file. That's something that is more effectively handled by a plug-in in your FE or by a stand alone logging program.
OSDash could be more of a service that is relayed to users in-dash systems or to other vendors.
It would make sense if OSDash were a web service and all FEs or even just your browser could access. And in reverse, it could accept your data that is being logged by your in-dash.
Here is a link that was listed in the CF plug-in contest thread (I think that is where I found it)
To get some ideas rolling: web APIs
A standard example:
Using the OBD data as an example you could keep track of speed, mileage and general maintenance of your fleet vehicles. Continuing with fleet vehicles you could also tag their gps to make sure they are busy bees instead of hot dog shop junkies.
If I were to take this to the dealer level, I could keep an eye on your regular maintenance and send out those friendly 3,oookm oil change post cards. Or even have your parts waiting or at least in transit to dealer since they have error codes that could clue them in before your car even reaches the mechanic / dealer by tow truck.
The movie database idea that just came up.
Where would I go with this?
* come up with a list of basic services that could provided by the server
* come up with a list of services that could be pushed from the in-dash to the server
* get people on board to create a plug-ins for the various FEs
* find data supplier services to come on-board so that you can provide more server based services
... Still need to think about this some more ...
Like brought up in the movies thread...this is where you will hit problems. Supplying data costs money (for server maintenance, bandwidth, developer time, etc)...theres really no incentive for a data provider to use OSDash-it costs them money with no return. Which is why in many cases OSDash type proxies are explicitly banned by their TOS.
Originally Posted by SapporoGuy
Just because some sources request payment, would that mean that other sources will also request the same?
The way I see it, a customer receives the data and then makes a decision to purchase or not. This means that the data has a value to the supplier. Therefore, we should be NOT be short selling our users who in reality are their customers.
If we can not source the data, what is stopping us from creating a service that would convince companies to actually contact us to provide them a chance?
lolo, I'm sure porn companies would love to stream to a new environment ... I don't think I'd like to be distracted that much though ;)
I think there may be some slight confusion about what osdash is intending to provide and how it is to be used. Creating an osdash service to talk to twitter or facebook doesn't provide anything. But look at how we are using it now: Live-traffic/Location information and remote control. None of these services currently exist for free outside of osdash. I've coded bluemonkey to take advantage of at least the traffic bits. I'm working on making it work with the remote control.
In other words, OSDash should be used to provide web services that either don't exist, or exist but because of stringent TOS, are impossible for us to use in any useful way. These services are offered to forum members via their favorite frontend, *if* that frontend implements those services via some plugin of some sort (or built in, I don't care how they do it...).
We are backing off of the original complexity of the server a bit, yes. The way we are using it now is natural evolution based on need.
Actually, trip might be right. Evolution will get us there.
I'm gonna throw this in the mix.
Maybe, OSDash should be developed in sections?
[no particular order or importance]
I.) web FE
II.) tie-up with content providers
III.) create content to fill in the gaps
IV.) plug-in (will need content)
Thats exactly what I was pushing for....I think in those areas OSDash can really thrive... its better to put development effort into services that don't exist elsewhere then to try re-inventing the wheel.
Originally Posted by tripzero
and thats kind of what im saying should be avoided
Originally Posted by SapporoGuy