|
The BBB has better specs, I believe. You might want to check out odroid[^] Quad core!
Marc
|
|
|
|
|
That odroid looks like a neat piece of kit. But I'm happy to sacrifice performance for market share on this. I only need the thing to run a couple perl scripts.
|
|
|
|
|
Except for graphics, the GPU on a RPi is better.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
Is it any better than running on Raspberry Pi? I recall that was quite a horror and not worth the bother
I guess the Beagle series are higher spec?
|
|
|
|
|
|
The BeagleBone really looks good. I've got to get hold of one, I can already think of a few projects for it
|
|
|
|
|
What problem did you have with the Pi? I've set up a few and never had any difficulty.
|
|
|
|
|
Restful Api Model Language[^]
Ever heard of it? Ever use it?
Supposedly "better" than web services (SOAP/WSDL). I don't know about that, but my client suggested I might want to use it for a project. As far as I can tell, it's not gaining much traction.
Marc
|
|
|
|
|
Never heard of it. Can't see the point of it (mind you I only spent 2 mins on the website) and anything which talks about 'The Application Programming eXperience, or APX' should probably be mercilessly destroyed! My APX is going bad-to-average today by the way, how's yours?
I've done a little bit of REST and I thought the idea of it was to simplify things. SOAP was too complicated (it is actually), and this was the answer. Now they want to create a whole new meta-language on top of it?
Hmm. That's my final thought.
Regards,
Rob Philpott.
|
|
|
|
|
Thanks for sharing, I'm doing a lot of Restful interfaces at the moment for interfacing Android to Windows (WCF Rest).
|
|
|
|
|
Well, there's another one I've not heard of. While some parts of it look quite promising, it looks to be a bit overkill to me. My RESTful APIs, nowadays, tend to be a node.js express application picking up the requests and handling them. It's very easy to use. For a moment, I was prepared to be impressed by this but I realised that the versioning they were talking about had absolutely nothing to do with API versioning - which would have been something I would be very interested in.
|
|
|
|
|
Pete O'Hanlon wrote: the versioning they were talking about had absolutely nothing to do with API versioning - which would have been something I would be very interested in.
Huh, I hadn't caught that. I thought it was API versioning as well and thought, oh, that's a nifty feature.
Marc
|
|
|
|
|
Oh yes. That would have simplified my life immensely.
|
|
|
|
|
What do you see as the advantage to REST vs. something like SOAP? Mind you, from what I've been reading, REST is an architecture and SOAP is a protocol, so I think it's a bit like comparing apples and oranges.
But from what I've been reading regarding REST, I just don't get it. Looks like nothing more than HTTP get/post commands.
Marc
|
|
|
|
|
That's pretty much what it is, HTTP commands; but don't forget UPDATE and DELETE commands. I like being able to quickly test my APIs through CURL. Yes, SOAP gives you the object wrapping that you don't really get with REST, but REST provides a simpler, more ubiquitous architecture.
|
|
|
|
|
So does that mean that you effectively need a web server running, rather than "just a" web service?
Marc
|
|
|
|
|
Basically yes. But as I use node most of the time for the back end now, this isn't an issue as node acts as my server.
|
|
|
|
|
Pete O'Hanlon wrote: But as I use node most of the time for the back end now, this isn't an issue as node acts as my server.
That's what I figured. Thanks for the info!
Marc
|
|
|
|
|
Sounds like an attempt to make REST more SOAPy.
I don't know why REST seems to be gaining popularity when SOAP is superior.
|
|
|
|
|
Eggbert Bartholomew Bligh wrote: I don't know why REST seems to be gaining popularity when SOAP is superior.
There are thousands of people who prefer to have a rest than use soap.
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
|
|
|
|
|
chriselst wrote: than use soap.
Clearly you are a SOAP denier, and don't like tidy clean SOAP objects.
|
|
|
|
|
XML and the XSD solved the problem of interchange. It easy, verifiable, and simple. Yet, JSON works so much better with Javascript and Java has such poor native XML support when compared to .NET (and no start-up developer uses .NET [*rolls eyes*]
So all of the problems that would have been solved by rest accepting XML are now being redone in order to better support HTML 5 and Javascript, as well as other "modern" languages which lack truly amazing support of XML.
(Don't fool yourself, XML in .NET is leaps and bounds ahead of the rest)
|
|
|
|
|
|
If you have never read a book on the subject it gives you the ability to invent from scratch.
|
|
|
|
|
Although they gave neither ANSWER nor SOLUTION.
However...Well done Motor Viper.
The answer is DAYDREAMS.
---------------------------------
Obscurum per obscurius.
Ad astra per alas porci.
Quidquid latine dictum sit, altum videtur .
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
