Sponsored Content
Full Discussion: Vue.js Steam Chat
Top Forums Web Development Vue.js Steam Chat Post 303034102 by Neo on Thursday 18th of April 2019 05:58:50 AM
Old 04-18-2019
Today, I'm back in a tech session with PubSub about loading message history when someone starts the session / joins the page.

Quote:
..... and so when I console log time, I can see that the channel saves all the prior history after the pages is loaded or reloaded; but if I reload the page, the history is not loaded from the server, as if the PubNub Storage API is not persistent across sessions, because the expected behavior is when someone opens their app and this page, they will see the chat / message history on that channel; so there seems to be no "autoload' really happening when the session starts.

I have just console logged the above, and of course the this.ch1 array grows with each message, but that information is gone when the page is reloaded, so there is really no history at all coming from the PubSub API when someone joins the channel. The only "history" is in a session which has already started, and this is not useful at all, because we need for users to see the message history on the channel when they first join the channel.
 

5 More Discussions You Might Find Interesting

1. Web Development

Can you embed Skype or any other video chat/chat program into a webpage?

Hi, I am trying to embed Skype or any other video chat/chat program into a webpage. Has anyone had success doing this? or know how? Thanks Phil (2 Replies)
Discussion started by: phil_heath
2 Replies

2. What is on Your Mind?

Very Funny and Somewhat Amazing 2006 Chat Bot Chat

Working on the badging system, Just found this old thread for 2006 and started reading it. ROTFL ... what a great discussion between forum members and our chat bot Gollum "back in the good old days"... You must check this out if you want a laugh and big smile: ... (1 Reply)
Discussion started by: Neo
1 Replies

3. Web Development

Simple Vue.js Component to Redirect to External Web Page Using Vue Router

Vue Router has some quirks and on of the quirks is that it is not reliable when adding external links using the vue-router library. After struggling with many solutions, I have found that creating a simple Vue.js component like this one seems to work the best (so far): Component Example: ... (0 Replies)
Discussion started by: Neo
0 Replies

4. Web Development

Vue JS 2 Tutorial by The Net Ninja: A Recommended Vue.js Video Tutorial Series

A number of people have asked me how to get started with Vue.js and my reply before today was to Google "Vue.js". That has changed and my recommendation to anyone who wants to learn the fastest growing, easiest to learn and use Vue.js web dev framework is to watch this video tutorial series: ... (0 Replies)
Discussion started by: Neo
0 Replies

5. Web Development

Documenting Installation Problem with vue-beautiful-chat

REF: https://github.com/mattmezza/vue-beautiful-chat $ git clone https://github.com/mattmezza/vue-beautiful-chat.git Cloning into 'vue-beautiful-chat'... remote: Enumerating objects: 534, done. remote: Total 534 (delta 0), reused 0 (delta 0), pack-reused 534 Receiving objects: 100%... (2 Replies)
Discussion started by: Neo
2 Replies
condor_convert_history(1)				      General Commands Manual					 condor_convert_history(1)

Name
       condor_convert_history Convert - the history file to the new format

Synopsis
       condor_convert_history[-help]

       condor_convert_historyhistory-file1[history-file2...]

Description
       As  of  Condor  version 6.7.19, the Condor history file has a new format to allow fast searches backwards through the file. Not all queries
       can take advantage of the speed increase, but the ones that can are significantly faster.

       Entries placed in the history file after upgrade to Condor 6.7.19 will automatically be saved in the new format. The new format adds infor-
       mation  to  the	string which distinguishes and separates job entries. In order to search within this new format, no changes are necessary.
       However, to be able to search the entire history, the history file must be converted  to  the  updated  format.	condor_convert_historydoes
       this.

       Turn the condor_schedddaemon off while converting history files. Turn it back on after conversion is completed.

       Arguments  to  condor_convert_historyare  the  history  files to convert. The history file is normally in the Condor spool directory; it is
       named  history . Since the history file is rotated, there may be multiple history files, and all of them should be converted. On Unix plat-
       form variants, the easiest way to do this is:

       cd `condor_config_val SPOOL`
       condor_convert_history  history*

       condor_convert_historymakes  a  back  up  of each original history files in case of a problem. The names of these back up files are listed;
       names are formed by appending the suffix  .oldver to the original file name. Move these back up files to a directory other than	the  spool
       directory. If kept in the spool directory, condor_historywill find the back ups, and will appear to have duplicate jobs.

Exit Status
       condor_convert_historywill exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure.

Author
       Condor Team, University of Wisconsin-Madison

Copyright
       Copyright  (C)  1990-2012  Condor  Team,  Computer  Sciences Department, University of Wisconsin-Madison, Madison, WI. All Rights Reserved.
       Licensed under the Apache License, Version 2.0.

       See the Condor Version 7.8.2 Manualor http://www.condorproject.org/licensefor additional notices. condor-admin@cs.wisc.edu

								  September 2012					 condor_convert_history(1)
All times are GMT -4. The time now is 12:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy