mobilehero-archive/titanium-eventsource

⭐ Axway Amplify module to implement EventSource for Appcelerator Titanium SDK

Preparing for end of Axway

👇   support for Amplify Cloud and Mobile   👇

🪦   RIP Axway Amplify Titanium (2010 - 2022)

🪦   RIP Axway Amplify Cloud Services (2012 - 2022)

🪦   RIP Axway Amplify Crash Analytics (2015 - 2022)

---

🛑    Axway support for Amplify products has ended for most products related to mobile and cloud.

A few of the open-source versions of Axway Amplify products will live on after Axway Amplify End-of-Life (EOL) announcements. However, all closed-source projects and most open-source projects are now dead.

 

👉    A group of Axway employees, ex-Axway employees, and some developers from Titanium community have created a legal org and now officially decide all matters related to future of these products.

 

---

API FAQ:

• API Best Practices
• What is API Security?
• OWASP Top 10 List for API Security
• What is API Security?
• Top API Trends for 2022
• What is a Frankenstein API?
• What is a Zombie API?
• API Developer Experience
• API Cybersecurity 101
• YouTube API Videos
• YouTube API Shorts Videos

 

  ↑ Watch video on YouTube ↑

 

 

---

 

 

@titanium/eventsource

Implementation of EventSource for Axway Amplify Titanium Native mobile apps

• API FAQ:
• 📝 Description
• 🚀 Getting Started
• 🔗 Related Links
• 📚 Learn More
• 📣 Feedback
• ©️ Legal

📝 Description

Server-Sent Event (SSE) streaming communication requires an implementation of EventSource and currently, no other EventSource polyfill exists for Titanium Native mobile apps. This package was written to be fully spec compliant: https://html.spec.whatwg.org/multipage/server-sent-events.html More features may be added to this client but goal is to keep it compliant.

Titanium EventSource is based on EventSource Polyfill by Matt Krick.

🚀 Getting Started

This module is meant to be used with Axway Amplify Titanium Native mobile apps

There are several ways this module can be used by Axway Amplify Titanium. It is likely that the package or library you are using for SSE already has this package as a dependency, in which case, you do not need to do anything further.

Please ensure there is a package.json file in the target directory. If there is not one present, you can create one with npm init.

If you are building an SSE module yourself and wish to use Titanium EventSource or you wish to install this in an app using Titanium Turbo, you can execute this in the project root directory:

npm install @titanium/eventsource

If you wish to install this in a Titanium Alloy app, you an install this by executing the following in the project root directory:

cd app
npm install @titanium/eventsource

🔗 Related Links

⭐ Titanium Mobile - Open-source tool for building powerful, cross-platform native apps with JavaScript.
⭐ Titanium Alloy - MVC framework built on top of Titanium Mobile.
⭐ Appcelerator - Installer for the Appcelerator Platform tool
⭐ Titanium Turbo - Variation of Titanium Alloy that adds some enhancements and customizations for rapid development.
⭐ Geek Mobile Toolkit - Toolkit for creating, building, and managing mobile app projects.

📚 Learn More

⭐ Axway Developer Portal
⭐ Axway Developer Blog

📣 Feedback

Have an idea or a comment? Join in the conversation here!

©️ Legal

Alloy is developed by Appcelerator and the community and is Copyright © 2012-Present by Appcelerator, Inc. All Rights Reserved.

Alloy is made available under the Apache Public License, version 2. See their license file for more information.

Appcelerator is a registered trademark of Appcelerator, Inc. Titanium is a registered trademark of Appcelerator, Inc. Please see the LEGAL information about using trademarks, privacy policy, terms of usage and other legal information at http://www.appcelerator.com/legal.

titanium-eventsource's Issues

update latest dependencies

update latest dependencies

Your .dependabot/config.yml contained invalid details

Dependabot encountered the following error when parsing your .dependabot/config.yml:

The property '#/update_configs/0/ignored_updates/0' contains additional properties ["dependency_name"] outside of the schema when none are allowed
The property '#/update_configs/0/ignored_updates/0/match' of type null did not match the following type: object. Is the following line indented correctly?

Please update the config file to conform with Dependabot's specification using our docs and online validator.

You can mention @dependabot in the comments below to contact the Dependabot team.