faye_shards 0.1.0 → 0.1.1

Sign up to get free protection for your applications and to get access to all the features.
data/README.rdoc CHANGED
@@ -64,7 +64,7 @@ So, in my example for production I have 2 Faye instances listening to ports 4200
64
64
  == Usage
65
65
 
66
66
  URL for Faye's client-side JS (unless you store it somewhere on diff storage) is returned by this methos:
67
- FayeShards.shard(current_user.id).js_url
67
+ FayeShards.shard(current_user.id).js_url(request.ssl?)
68
68
 
69
69
  Module <code>FayeShard::User::Faye</code> which can be included to your User model provides method <tt>faye_channel</tt> which returns unique channel id for user. If you do not want to include module to your model - you need to manage unique channels for users yourself.
70
70
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.1.0
1
+ 0.1.1
data/faye_shards.gemspec CHANGED
@@ -5,7 +5,7 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = %q{faye_shards}
8
- s.version = "0.1.0"
8
+ s.version = "0.1.1"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Alex Kazeko"]
@@ -24,8 +24,10 @@ module FayeShard
24
24
 
25
25
  # Returns default client JS url
26
26
  #
27
- def js_url
28
- url + '.js'
27
+ # * <tt>https</tt>:: Specifies whether to use SSL connection or not
28
+ #
29
+ def js_url(https = false)
30
+ url(https) + '.js'
29
31
  end
30
32
 
31
33
  # Local url, needed for RoR <-> Faye communication
metadata CHANGED
@@ -1,13 +1,13 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: faye_shards
3
3
  version: !ruby/object:Gem::Version
4
- hash: 27
4
+ hash: 25
5
5
  prerelease: false
6
6
  segments:
7
7
  - 0
8
8
  - 1
9
- - 0
10
- version: 0.1.0
9
+ - 1
10
+ version: 0.1.1
11
11
  platform: ruby
12
12
  authors:
13
13
  - Alex Kazeko