The document defines a ChatContact class that implements PropertyBusinessObject and represents contacts in a messaging app. It includes properties for contact details like id, name, photo, groups, and messaging metadata. Methods set up indexing and image processing for the photo property.
The document describes code for implementing the server-side functionality of a WhatsApp clone. It includes classes for representing users, messages, and server connections. The Server class initializes user and message data from files, handles login/signup, and establishes a websocket connection for real-time messaging. It can send and receive messages when connected, or queue messages when offline.
This document contains code for a Java web application that allows users to submit a registration form with their first name, last name, and email address. The form submission is handled by a JSP page that inserts the user details into a MySQL database using Java and JDBC. It then queries the database and displays the stored users in an HTML table. The code includes classes for the User object model and a SQLDBUtil class for database operations like insertion, updating, and checking if a user already exists by email.
The document describes a program for a multi-client chat client-server application using Java graphical programming. It includes the code for the ChatServer class that handles connections from multiple clients and broadcasts messages. It also includes the code for the ChatClient class that allows a client to connect to the server, send and receive messages, and view an online users list. The program allows for real-time text communication between multiple clients connected to a central server.
The document summarizes features in C# 10 and beyond, including records, required properties, parameter null checking, pattern matching, lambda improvements, and value tuple deconstruction. It also discusses how to run samples and provides information about the presenter, Moaid Hathot. Key C# 10 features covered are records, properties, parameter null checking, pattern matching, and lambda improvements. The document promotes less code through features like file-scoped namespaces and global using directives. It concludes with a discussion of abstract data types and static abstract members in interfaces.
The easy way to develop Java applications has always been the standard stack (Spring, JEE, SQL) that confirms the LAMP equivalent in Java-speak. This presentation compares this model with a real use case based on Guice, Jersey and AppEngine.
Creating a Facebook Clone - Part XIX - Transcript.pdfShaiAlmog1
Â
The document describes the implementation of a Post entity and related classes for the backend of a Facebook clone. It includes:
1) A Post entity with fields like user, date, title, content, visibility, styling, comments, and likes.
2) Post, Comment, and related DAO classes to transfer data to and from clients.
3) PostRepository and CommentRepository interfaces extending CrudRepository for database operations.
4) Methods in PostRepository like findPostsByUser() and findAllPostsByUser() to retrieve posts by user with paging support.
The Duck Teaches Learn to debug from the masters. Local to production- kill ...ShaiAlmog1
Â
The document outlines an agenda for a workshop on debugging techniques. The workshop covers installing tools, flow and breakpoints debugging, watching variables, Kubernetes debugging, and developer observability. Key techniques discussed include tracepoints, memory debugging, exception breakpoints, object marking, and logs, snapshots, and metrics for observability. The goal is to teach practical debugging skills that can be applied at scale in production environments like Kubernetes.
The document describes code for implementing the server-side functionality of a WhatsApp clone. It includes classes for representing users, messages, and server connections. The Server class initializes user and message data from files, handles login/signup, and establishes a websocket connection for real-time messaging. It can send and receive messages when connected, or queue messages when offline.
This document contains code for a Java web application that allows users to submit a registration form with their first name, last name, and email address. The form submission is handled by a JSP page that inserts the user details into a MySQL database using Java and JDBC. It then queries the database and displays the stored users in an HTML table. The code includes classes for the User object model and a SQLDBUtil class for database operations like insertion, updating, and checking if a user already exists by email.
The document describes a program for a multi-client chat client-server application using Java graphical programming. It includes the code for the ChatServer class that handles connections from multiple clients and broadcasts messages. It also includes the code for the ChatClient class that allows a client to connect to the server, send and receive messages, and view an online users list. The program allows for real-time text communication between multiple clients connected to a central server.
The document summarizes features in C# 10 and beyond, including records, required properties, parameter null checking, pattern matching, lambda improvements, and value tuple deconstruction. It also discusses how to run samples and provides information about the presenter, Moaid Hathot. Key C# 10 features covered are records, properties, parameter null checking, pattern matching, and lambda improvements. The document promotes less code through features like file-scoped namespaces and global using directives. It concludes with a discussion of abstract data types and static abstract members in interfaces.
The easy way to develop Java applications has always been the standard stack (Spring, JEE, SQL) that confirms the LAMP equivalent in Java-speak. This presentation compares this model with a real use case based on Guice, Jersey and AppEngine.
Creating a Facebook Clone - Part XIX - Transcript.pdfShaiAlmog1
Â
The document describes the implementation of a Post entity and related classes for the backend of a Facebook clone. It includes:
1) A Post entity with fields like user, date, title, content, visibility, styling, comments, and likes.
2) Post, Comment, and related DAO classes to transfer data to and from clients.
3) PostRepository and CommentRepository interfaces extending CrudRepository for database operations.
4) Methods in PostRepository like findPostsByUser() and findAllPostsByUser() to retrieve posts by user with paging support.
Similar to Creating a Whatsapp Clone - Part III.pdf (20)
The Duck Teaches Learn to debug from the masters. Local to production- kill ...ShaiAlmog1
Â
The document outlines an agenda for a workshop on debugging techniques. The workshop covers installing tools, flow and breakpoints debugging, watching variables, Kubernetes debugging, and developer observability. Key techniques discussed include tracepoints, memory debugging, exception breakpoints, object marking, and logs, snapshots, and metrics for observability. The goal is to teach practical debugging skills that can be applied at scale in production environments like Kubernetes.
Session 1 - Intro to Robotic Process Automation.pdfUiPathCommunity
Â
👉 Check out our full 'Africa Series - Automation Student Developers (EN)' page to register for the full program:
https://bit.ly/Automation_Student_Kickstart
In this session, we shall introduce you to the world of automation, the UiPath Platform, and guide you on how to install and setup UiPath Studio on your Windows PC.
đź“• Detailed agenda:
What is RPA? Benefits of RPA?
RPA Applications
The UiPath End-to-End Automation Platform
UiPath Studio CE Installation and Setup
đź’» Extra training through UiPath Academy:
Introduction to Automation
UiPath Business Automation Platform
Explore automation development with UiPath Studio
👉 Register here for our upcoming Session 2 on June 20: Introduction to UiPath Studio Fundamentals: https://community.uipath.com/events/details/uipath-lagos-presents-session-2-introduction-to-uipath-studio-fundamentals/
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
Â
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
Â
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Fueling AI with Great Data with Airbyte WebinarZilliz
Â
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
Â
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Â
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
​​Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
​
​Facebook(Meta): https://www.facebook.com/mydbops/
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Â
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Â
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Â
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Â
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
2. package com.codename1.whatsapp.model;
import java.util.List;
public interface ServerMessages {
public void connected();
public void disconnected();
public void messageReceived(ChatMessage m);
public void userTyping(String contactId);
public void messageViewed(String messageId, List<String> userIds);
}
ServerMessages
3. package com.codename1.whatsapp.model;
import java.util.List;
public interface ServerMessages {
public void connected();
public void disconnected();
public void messageReceived(ChatMessage m);
public void userTyping(String contactId);
public void messageViewed(String messageId, List<String> userIds);
}
ServerMessages
4. package com.codename1.whatsapp.model;
import java.util.List;
public interface ServerMessages {
public void connected();
public void disconnected();
public void messageReceived(ChatMessage m);
public void userTyping(String contactId);
public void messageViewed(String messageId, List<String> userIds);
}
ServerMessages
5. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
6. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
7. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
8. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
9. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
10. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
11. public class ChatContact implements PropertyBusinessObject {
public final Property<String, ChatContact> id = new Property<>("id");
public final Property<String, ChatContact> localId =
new Property<>("localId");
public final Property<String, ChatContact> phone =
new Property<>("phone");
public final Property<Image, ChatContact> photo =
new Property<>("photo", Image.class);
public final Property<String, ChatContact> name =
new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
ChatContact
12. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
13. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
14. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
15. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
16. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
17. new Property<>("name");
public final Property<String, ChatContact> tagline =
new Property<>("tagline");
public final Property<String, ChatContact> token =
new Property<>("token");
public final SetProperty<String, ChatContact> members =
new SetProperty<>("members", String.class);
public final SetProperty<String, ChatContact> admins =
new SetProperty<>("admins", String.class);
public final LongProperty<ChatContact> muteUntil =
new LongProperty<>("muteUntil");
public final Property<String, ChatContact> createdBy =
new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
ChatContact
18. new Property<>("createdBy");
public final Property<Date, ChatContact> creationDate =
new Property<>("creationDate", Date.class);
public final Property<Date, ChatContact> lastActivityTime =
new Property<>("lastActivityTime", Date.class);
public final ListProperty<ChatMessage, ChatContact> chats =
new ListProperty<>("chat", ChatMessage.class);
private final PropertyIndex idx = new PropertyIndex(this, "ChatContact",
id, localId, phone, photo, name, tagline, token, members, admins,
muteUntil, createdBy, creationDate, lastActivityTime, chats);
@Override
public PropertyIndex getPropertyIndex() {
return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
ChatContact
19. return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
private static final float[] IMAGE_SIZES = {4f, 6.5f};
private static final Image[] maskImage = new Image[2];
private static final Object[] maskObject = new Object[2];
private static final EncodedImage[] placeholder = new EncodedImage[2];
private static Image createMaskImage(int size) {
Image m = Image.createImage(size, size, 0);
Graphics g = m.getGraphics();
g.setAntiAliased(true);
g.setColor(0xffffff);
g.fillArc(0, 0, size - 1, size -1, 0, 360);
return m;
}
ChatContact
20. return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
private static final float[] IMAGE_SIZES = {4f, 6.5f};
private static final Image[] maskImage = new Image[2];
private static final Object[] maskObject = new Object[2];
private static final EncodedImage[] placeholder = new EncodedImage[2];
private static Image createMaskImage(int size) {
Image m = Image.createImage(size, size, 0);
Graphics g = m.getGraphics();
g.setAntiAliased(true);
g.setColor(0xffffff);
g.fillArc(0, 0, size - 1, size -1, 0, 360);
return m;
}
ChatContact
21. return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
private static final float[] IMAGE_SIZES = {4f, 6.5f};
private static final Image[] maskImage = new Image[2];
private static final Object[] maskObject = new Object[2];
private static final EncodedImage[] placeholder = new EncodedImage[2];
private static Image createMaskImage(int size) {
Image m = Image.createImage(size, size, 0);
Graphics g = m.getGraphics();
g.setAntiAliased(true);
g.setColor(0xffffff);
g.fillArc(0, 0, size - 1, size -1, 0, 360);
return m;
}
ChatContact
22. return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
private static final float[] IMAGE_SIZES = {4f, 6.5f};
private static final Image[] maskImage = new Image[2];
private static final Object[] maskObject = new Object[2];
private static final EncodedImage[] placeholder = new EncodedImage[2];
private static Image createMaskImage(int size) {
Image m = Image.createImage(size, size, 0);
Graphics g = m.getGraphics();
g.setAntiAliased(true);
g.setColor(0xffffff);
g.fillArc(0, 0, size - 1, size -1, 0, 360);
return m;
}
ChatContact
23. return idx;
}
public ChatContact() {
idx.setExcludeFromJSON(photo, true);
}
private static final int SMALL_IMAGE = 0;
private static final int LARGE_IMAGE = 1;
private static final float[] IMAGE_SIZES = {4f, 6.5f};
private static final Image[] maskImage = new Image[2];
private static final Object[] maskObject = new Object[2];
private static final EncodedImage[] placeholder = new EncodedImage[2];
private static Image createMaskImage(int size) {
Image m = Image.createImage(size, size, 0);
Graphics g = m.getGraphics();
g.setAntiAliased(true);
g.setColor(0xffffff);
g.fillArc(0, 0, size - 1, size -1, 0, 360);
return m;
}
ChatContact