I am just experimenting with networking. I am trying to build small apps to
get the inside.
I firtsly thougth that Distributed Objects and remote procedure calling was
the more elegant way
to communicate over a LAN.
Then i found that Distributed Objects won't work on iOS. I am still in the
search
If you are targeting at remote procedure calling across Internet I have a
library CGIJSONObjects that wraps REST-style JSON-based HTTP remote calls into
objects. Server side language is not important. I used it to interface a server
using Java servlets.
Sent from my iPhone
> On May 1, 2014, at
On Wed, Apr 30, 2014, at 04:30 PM, Jens Alfke wrote:
>
> On Apr 30, 2014, at 4:00 PM, Jonathan Hull wrote:
>
> > I also find that it is good practice to set variables returned by reference
> > to nil before passing them.
> > NSError *error = nil;
> > Otherwise, they will contain garbage, and ca
On Apr 30, 2014, at 4:00 PM, Jonathan Hull wrote:
> I also find that it is good practice to set variables returned by reference
> to nil before passing them.
> NSError *error = nil;
> Otherwise, they will contain garbage, and cannot reliably be tested to see if
> the value was set.
That’s sti
On Apr 30, 2014, at 16:00 , Jonathan Hull wrote:
> I also find that it is good practice to set variables returned by reference
> to nil before passing them.
>
> NSError *error = nil;
>
> Otherwise, they will contain garbage, and cannot reliably be tested to see if
> the value was set.
This p
I also find that it is good practice to set variables returned by reference to
nil before passing them.
NSError *error = nil;
Otherwise, they will contain garbage, and cannot reliably be tested to see if
the value was set. Andy is right though, that it is better to test whether
jsonObject is
Thanks Andy and Jens!
Op Apr 30, 2014, om 10:07 PM heeft Andy Lee het volgende
geschreven:
> On Apr 30, 2014, at 3:21 PM, Jens Alfke wrote:
>> On Apr 30, 2014, at 8:20 AM, Diederik Meijer | Ten Horses
>> wrote:
>>
>>> Now here is the problem: although the JSON parses fine and populates a
Thanks Steve, that's promising, most likely something wrong in my
NSURLConnection code then, or the way I call it.
I don't think there's anything trailing in the JSON content, there really
isn'tt much in there his is the api server code:
format('d.m.Y');
$Hyperlink = $row['hyperlink
On Apr 30, 2014, at 3:21 PM, Jens Alfke wrote:
> On Apr 30, 2014, at 8:20 AM, Diederik Meijer | Ten Horses
> wrote:
>
>> Now here is the problem: although the JSON parses fine and populates a
>> UITableView without any issues, I am still getting the following error:
>
> If the JSON parsed fin
On Apr 30, 2014, at 2:39 PM, Jens Alfke wrote:
> Yes. DO between computers (over TCP) was never really supported on OS X,
It most certainly was supported, and useable on a LAN (and even on a WAN over
VPN, did not try it in the wild).
> and has a number of security and reliability problems
Tr
On Apr 30, 2014, at 3:21 PM, Jens Alfke wrote:
> You’ll need to do some detective work to find out what function call that
> error is really coming from. At that point you can set a breakpoint and look
> at the input data.
Maybe for debugging purposes you could drop in an open-source JSON parse
On Apr 30, 2014, at 12:14 PM, Steve Christensen wrote:
> Doing a brief search, it seems like when others are running into this error,
> they’re working with JSON data that really does have garbage at the end.
Yeah, I’ve been doing a ton of JSON work with NSJSONSerialization for as long
as it’
On Apr 30, 2014, at 11:19 AM, Costas Chatzinikolas
wrote:
> So if i want to create two apps (one for Mac OS X - one for iOS) that speak
> to each other,
> i have to use sockets. Am i correct?
Yes. DO between computers (over TCP) was never really supported on OS X, and
has a number of securit
I’m already doing downloads in my app using NSURLSession so I used my existing
code to download and decode the data returned by the URL below and didn’t get
an error. I am building against iOS 7.1 and I tried it out in the simulator.
Doing a brief search, it seems like when others are running in
On Apr 30, 2014, at 8:20 AM, Diederik Meijer | Ten Horses
wrote:
> Now here is the problem: although the JSON parses fine and populates a
> UITableView without any issues, I am still getting the following error:
If the JSON parsed fine, then the error must be coming from somewhere else. A
ca
So if i want to create two apps (one for Mac OS X - one for iOS) that speak
to each other,
i have to use sockets. Am i correct?
2014-04-30 17:16 GMT+03:00 Jens Alfke :
>
> On Apr 29, 2014, at 11:49 PM, Costas Chatzinikolas <
> costas.chatziniko...@gmail.com> wrote:
>
> One quick question: DO API
Hi all,
I have Googled this issue for hours and tried various solutions suggested at
Stackoverflow, but can't seem to solve the following problem.
I am pulling JSON from here:
http://www.tenhorses.com/apps/meijburg/dotTAXDataHandler/dotTAXtaxNotesAPI.php
Both JSONLint, http://jsonformatter.cur
On Apr 29, 2014, at 11:49 PM, Costas Chatzinikolas
wrote:
> One quick question: DO API is not available on iOS. Do you know if
> NSXPCConnection is?
No, because iOS apps aren’t allowed to create new processes, so there would be
no agents for you to communicate with.
—Jens
__
On 30 Apr 2014, at 00:52, Gordon Apple wrote:
> We would like to get a recommendation on the best way to generate a help
> system for a fairly complex application.
You might also try techwrl-list, they're the experts on help systems:
http://www.techwr-l.com/frequently-asked-questions.html#subs
Hi Costas,
I'd be interested in hearing the results of you following up NSXPCConnection.
When I read through the documentation about a year ago, it is focussed around
providing a xpcservice which is a bundled executable within an application, and
the application communicates with it using NSXPC
20 matches
Mail list logo
