Yep I agree there, you should create thumbs that
are totally separate. Otherwise your sending megs instead of
K. And you can create the thumbs on new user signup. I've done
that, and it woks really well. Really need to check your image sizes.
On Apr 7, 5:18 am, Harold A. Giménez Ch.
wrote:
> To
y set down in a large screen, and have
all
the reference I need, and get things done. I've done 500+ table rails
app in aviation, so lot of what you saying seems really simple to me.
drop me a mail at glennswest at yahoo dot come dot sg
On Apr 7, 4:35 am, "eborhood.com" wrote:
Yes you would normally update pings as they occur, unless your
thinking of submitting
a xml and doing a bulk update. So the "pinger" is doing a butch of
pings, then
sending the results to the backend?
Then you just need to convert a local array to a xml file and submit
it to your Restful web app.
I've added a blog article of my network scanner.
If you need further help let me know.
http://mentalpagingspace.blogspot.com/2009/04/network-monitor-as-windows-service-in.html
On Apr 7, 10:31 am, Junior Junior wangsa wrote:
> hi..
>
> i'm new at ruby on rails..
> first i have a table with a c
witch port, and using SNMP to the switch to do discovery of
devices.
The moral of this is break you ping into a separate process/task. Then
poll yours AP's
and update there status with ActiveRecord.
If you need some help, I can certainly give you some pointers.
glennswest at yahoo dot com d
not going to be your bottleneck for a while,
its more the
style.
Why dont I train you a bit. We can do a screen share/skype session.
On Apr 6, 9:27 pm, Adam Akhtar
wrote:
> Thanks glennswest, im relatively new to rails. Whilst i think i
> understood what you said can you (or anyone else)
Just thinking, your scrape should probably be in a worker, stick the
results in
a db, Depending on what your using, you configure it to be a temp
table even.
Then in your search window you can do ajax based updated from the
scrape.
With the ability to then clear up the cache. You get more concurre
This is a "stateful" type processing, and you can do redirects after
each submit.
Also you can keep track of the time of the last state, and then use
rufus-scheduler to
run a cleanup task from time to time.
There is also a call in rails to let you redirect on the server, so on
the submit of step
Rails is single threaded, it processes one request at a time.
Unless you are using nginx/mongrel cluster.
You can have any number of users, but having a server call itself is
not a good thing. You want to get out of the controller quickly, not
be waiting on something. What you might want to do is
You can easily create a table, and stick it in as a row.
in rails sqlite is easy enough, if you site is bigger you
can use db2.
If its like most sites, you make a "result" table
that is associated to a user table.
--~--~-~--~~~---~--~~
You received this message bec
Your "code" is past being "old" in ruby and rails terms.
Almost everything has been updated/fixed and resolved.
I've got production sites that have been running for 6 months, with
a reboot at most once a month. (On windows). On linux,
no problem at all. Update and run it on passenger.
I run code
Here my "strategy" for such a app.
1. Export\copy the existing database schema, and a "snapshot" of the
data into your database of choice.
I usually use a ruby application at dbi level, or a rake task. On my
blog there are several reviews of doing this.
This also gets you a chance to "cleanup" th
It depends on "what" you have interest in doing.
For my applications, there database focused.
So here is the "getting" something going in the shortest possible
time.
1. Get the "Ruby Cookbook fro Oreilly". (Keep on your desk)
2. ProActive Record is another one I would keep handy.
3. Choose a pr
that
can
be developed by one guy in two weeks?
I've seen a few php developers that were ok, but its not something I'd
recommend a fortune 500 use to do a proper application.
On Oct 8, 10:09 am, "Maurício Linhares" <[EMAIL PROTECTED]>
wrote:
> On Tue, Oct 7, 2008 at 11:0
Yes, I tend to break each major part of my app, into a namespace.
If its a "top" tab on my menu, its a namespace.
It make life so much easier. So yes, admin is almost always
in every app. Espesially when you start having dozens to hundreds of
controllers. Havent quite got to having a "model" in di
Is Ruby Faster to Develop than PHP?
Yes (What 5 people did in a year, I did in a week)
Can I make my Rails App Faster than the "old" PHP APP?
Yes
Is Ruby the bottleneck?
No
Can I learn new things in ruby fast?
Yes
Can I get them into Production fast?
Yes
Can I scale applications to support bi
16 matches
Mail list logo
