Giter Site home page Giter Site logo

eventsource's Introduction

EventSource

Server-Sent Events for iOS and Mac

Travis

What does it do?

It creates a long-lived, unidirectional HTTP channel between your Cocoa app and a web server so that your app can receive events from the server.

Listening for Named Events

Subscribing to a named event is done via the addEventListener:handler: method, as shown below:

NSURL *serverURL = [NSURL URLWithString:@"http://127.0.0.1:8000/"];
EventSource *source = [EventSource eventSourceWithURL:serverURL];
[source addEventListener:@"hello_event" handler:^(Event *e) {
    NSLog(@"%@: %@", e.event, e.data);
}];

It's super simple and will be familiar to anyone who has seen any Server-Sent Events JavaScript code.

Listening for All Events

There's a onMessage: method that will receive all message events from the server.

NSURL *serverURL = [NSURL URLWithString:@"http://127.0.0.1:8000/"];
EventSource *source = [EventSource eventSourceWithURL:serverURL];
[source onMessage:^(Event *e) {
    NSLog(@"%@: %@", e.event, e.data);
}];

Listening for Connection State Changes

Additionally, there are onOpen:, onError:, and onReadyStateChanged: methods to receive connection state events.

NSURL *serverURL = [NSURL URLWithString:@"http://127.0.0.1:8000/"];
EventSource *source = [EventSource eventSourceWithURL:serverURL];
[source onError:^(Event *e) {
    NSLog(@"ERROR: %@", e.data);
}];

With the exception of the onError:, the event and data properties for these events will be null. Check the readyState property on the event.

Graceful Connection Handling

Reconnection attempts are automatic and seamless, even if the server goes go. How frequently reconnection attempts are made is controlled by the server by setting the retry key on its events.

Server Code

This is a simple Node.js app that will generate the Server-Sent Events. The events are created at a rate of one per second.

var http = require('http');

http.createServer(function (req, res) {
    res.writeHead(200, { 'Transfer-Encoding': 'chunked', 'Content-Type': 'text/event-stream' });
 
    setInterval(function() { 
        var now = new Date().getTime();
        var payload = 'event: hello_event\ndata: {"message":"' + now + '"}\n\n'; 
        res.write(payload); 
    }, 1000);
}).listen(8000);

The payload above doesn't include an id parameter, but if you include one it will be available in the Event object in your Cocoa code.

There is also a simple Go Server-Sent Events server.

Installation

The easiest way to get started is to use Carthage. Just add the following line to your Cartfile and the run carthage update from your terminal:

github "neilco/EventSource"

If you prefer Cocoapods, add this to your Podfile and then run pod install from your terminal:

pod 'EventSource'

Otherwise, just include the contents of the EventSource directory manually to your project.

Other bits

Contact

I'm @neilco on GitHub and I'm @neilco on Twitter.

License

MIT license

Copyright (c) 2013 Neil Cowburn (http://github.com/neilco/)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

eventsource's People

Contributors

neilco avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

eventsource's Issues

If server send a lot of event handler will not get call

If server send a lot of event handler will not get call, it will stuck on first for loop. Here is my hot-fix code.

- (void)connection:(NSURLConnection *)connection didReceiveData:(NSData *)data
{
    __block NSString *eventString = [[NSString alloc] initWithData:data encoding:NSUTF8StringEncoding];

    if ([eventString hasSuffix:@"\n\n"]) {
        dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_BACKGROUND, 0), ^{
            NSArray* eventArray = [eventString componentsSeparatedByString:@"\n\n"];
            for (NSString* sigleEventString in eventArray) {
                NSArray *components = [sigleEventString componentsSeparatedByString:@"\n"] ;
                Event *e = [Event new];
                e.readyState = kEventStateOpen;

                for (NSString *component in components) {
                    NSUInteger location = [component rangeOfString:@":"].location;
                    if (location != NSNotFound) {
                        NSString *dataPath = [component substringFromIndex:location+1];
                        dataPath = [dataPath stringByTrimmingCharactersInSet:[NSCharacterSet whitespaceAndNewlineCharacterSet]];
                        if ([component hasPrefix:@"id:"]) {
                            e.id = dataPath;
                        } else if ([component hasPrefix:@"event:"]) {
                            e.event = dataPath;
                        } else if ([component hasPrefix:@"data:"]) {
                            e.data = dataPath;
                        }

                    }
                }

                if (e.event != nil) {
                    NSArray *namedEventhandlers = listeners[e.event];
                    for (EventSourceEventHandler handler in namedEventhandlers) {
                        dispatch_async(dispatch_get_main_queue(), ^{
                            handler(e);
                        });
                    }
                }
            }
        });
    }
}

watchOS Support

Any plan to support the watchOS as well in the near future?

Received data splits if is too long

Extracted from #9 (comment)

My server returns data in single line. But if it is very large (a few dozen screens if use line-breaks, I may measure if needed), looks like URLSession calls didReceiveData with parts of payload. I found it here. So payload just comes broken.

Firebase observer using REST Api

I am building IOS application using firebase REST API. From the doc (Ref: https://firebase.google.com/docs/reference/rest/database/) it says that we can Stream from the REST API.I am not able to listen firebase events.When I run the app Only onOpen callback is called. When i changed the child value on firebase nothing happened on callback methods. Can you suggest me the way to observe the events?
I tried the following code:

    Auth.auth().currentUser?.getIDTokenForcingRefresh(true, completion: { (token, error) in
    let server : String =  "https://project-XXXXX.firebaseio.com/.json?auth=\(token!)"

    let eventSource: EventSource = EventSource(url: server)
    eventSource.onOpen {
        // When opened
        debugPrint("eventSource open")
    }

    eventSource.onError { (error) in
        // When errors
        debugPrint("error = \(error?.localizedDescription)")
    }
    eventSource.onMessage { (id, event, data) in
         debugPrint("data = \(data)")
        // Here you get an event without event name!
    }

    eventSource.addEventListener("child_added") { (id, event, data) in
           debugPrint("data = \(data)")
        // Here you get an event 'event-name'
    }
})

Continuously tries to reconnect.

Hi,
If I attempt to connect to a stream which I know will fail (Incorrect auth) the onError: method is called.
In this method I call [self.source close]; however I keep receiving onError: callbacks as if it's still trying to connect.

Calling [self.source close]; should surely stop any attempts to reconnect?

Calling [self.source close]; on any connections that are open, successfully closes them.

NSURLRequest timeout

I was having an issue with the event source disconnecting at regular intervals and determined that it was because the underlying NSURLRequest hadn't had its timeoutInterval set. After changing [NSURLRequest requestWithURL:] to [NSURLRequest requestWithURL: cachePolicy: timeoutInterval:], the connection stays open as expected. Perhaps it would make sense to change [EventSource initWithURL:] to [EventSource initWithURL: timeoutInterval:]?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.